PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-73259 cesanta CVE debrief

A remote attacker can send a crafted percent-encoded request path to a deployment using MG_ENABLE_DIRLIST and persuade a user to visit it. The mg_http_serve_dir() and listdir() path in src/http.c places the decoded request URI into the title and h1 elements without HTML entity encoding. The resulting reflected cross-site scripting executes in the Mongoose origin and can expose session data or perform actions as the victim.

Vendor
cesanta
Product
mongoose
CVSS
MEDIUM 5.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-20
Original CVE updated
2026-09-09
Advisory published
2026-08-20
Advisory updated
2026-09-09

Who should care

Defenders responsible for Mongoose deployments using MG_ENABLE_DIRLIST should assess exposure and prioritize upgrading to version 7.22. This includes reviewing current configurations, identifying potentially affected systems, and planning vendor-supported updates or mitigations through normal change control where exposure is confirmed. Security teams and vulnerability management teams should also review the official advisory and CVE record to validate the

Why it matters

Defenders should care about CVE-2026-73259 because it allows for reflected cross-site scripting in Mongoose deployments using MG_ENABLE_DIRLIST, potentially exposing session data or allowing actions as the victim. Verification of exposure and upgrading to version 7.22 are crucial.

  • Exposed session data through reflected cross-site scripting
  • Potential actions as the victim through reflected cross-site scripting
  • Verification of Mongoose deployments using MG_ENABLE_DIRLIST
  • Upgrade to Mongoose version 7.22 or later

Technical summary

The mg_http_serve_dir() and listdir() path in src/http.c places the decoded request URI into the title and h1 elements without HTML entity encoding, allowing for reflected cross-site scripting. This occurs in Mongoose deployments using MG_ENABLE_DIRLIST. The issue is fixed in version 7.22, but additional technical review is needed to understand affected scope and potential impact on specific configurations and user interactions within the Mongoose origin. A remote attacker can send a crafted percent-encoded request path to a deployment using MG_ENABLE_DIRLIST and persuade a user to visit it.

Defensive priority

Defenders should prioritize verifying exposure of Mongoose deployments using MG_ENABLE_DIRLIST and upgrading to version 7.22.

Recommended defensive actions

  • Verify if Mongoose deployments using MG_ENABLE_DIRLIST are exposed
  • Upgrade to Mongoose version 7.22 or later
  • Monitor for suspicious requests and user interactions
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Additional verification is needed to confirm affected versions and deployments. Defenders should verify if Mongoose deployments using MG_ENABLE_DIRLIST are exposed and review the official advisory for fix details. Limited source detail exists; explicit evidence limits apply.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-73259 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-73259

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-73259 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73259

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.