CVE-2026-2331
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file access feature, allowing access without authentication. This includes device parameter files, enabling an attacker to read and modify application settings, including customer-defined passwords. Additionally, exposure of the custom application directory may allow execution of arbitrary Lua code within the sandboxed AppEngine environment.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe AppEngine HTTP file access feature lacks proper authentication and authorization controls, exposing critical filesystem directories to unauthenticated attackers. This allows read/write access to device parameter files containing application settings and customer passwords, plus exposure of the custom application directory enabling arbitrary Lua code execution within the sandboxed environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AppEngine HTTP file access featureLocate the configuration or module that enables HTTP file access in your AppEngine deployment. This may be listed as HTTP file server, file transfer over HTTP, or web-based file browser in your system documentation or feature list.Affected if The HTTP file access feature is enabled and exposed as a web-accessible endpoint
-
Verify authentication requirement on HTTP file endpointsAttempt to access the HTTP file access URL endpoint without providing credentials, or review access logs to see if unauthenticated requests are permitted to file access paths.Affected if HTTP file access endpoints respond without requiring authentication or valid credentials
-
Inspect exposed directory structureList or enumerate the directories accessible through the HTTP file access feature using a web browser or HTTP client without authentication.Affected if Critical directories such as device parameter directories, application configuration directories, or custom application directories are visible or browsable
-
Check for sensitive file exposureAttempt to read device parameter files or application configuration files through the HTTP file access interface, or verify if these files are listed in the accessible directory listings.Affected if Device parameter files containing application settings or customer passwords are readable without authentication
-
Verify custom application directory accessDetermine if the custom application directory is accessible via the HTTP file access feature and whether files can be uploaded, modified, or executed.Affected if The custom application directory is exposed and allows read/write access enabling Lua code deployment
Your environment is affected if the AppEngine HTTP file access feature is enabled and permits unauthenticated access to device parameter files or custom application directories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement mandatory authentication and role-based authorization for all HTTP file access endpoints, restrict access to only necessary directories, and validate all file operations against proper access control policies.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2331 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data