CVE-2026-11841
Unauthenticated HTTP file access exposes filesystem, allows config tampering and Lua code execution.
Is CVE-2026-11841 being exploited?
Not confirmed. CVE-2026-11841 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-11841?
CVE-2026-11841 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-11841?
Not known from our data. No patch reference has been recorded for CVE-2026-11841, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-11841 affect?
CVE-2026-11841 affects Devices using AppEngine Fileaccess over HTTP, Embedded/IoT devices with AppEngine, Custom apps using AppEngine sandbox. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11841?
Disable HTTP Fileaccess, isolate affected devices, restrict network access, rotate credentials, apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated read/write to sensitive filesystem (modify passwords/configs) and arbitrary Lua code execution (RCE in AppEngine sandbox).
Immediate action required
- affected< 2.15.0
- affected< 5.4.0
- affected< 5.4.0
- affectedall versions
- affectedall versions
- affectedall versions
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.