CVE-2026-66296
Medium 5.1No known exploitationFix availableReflected XSS in oaskit's default HTML error handler
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 31% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Improper Neutralization of Input During Web Page Generation (XSS) vulnerability in lud oaskit allows reflected cross-site scripting via the default HTML error handler. Oaskit.ErrorHandler.Default.format_reason/4 and Oaskit.ErrorHandler.Default.reason_to_html/1 in lib/oaskit/error_handler/default.ex render request-validation failures as an HTML page whenever the request's Accept header contains html, interpolating request-controlled strings into that page without HTML escaping. The unescaped values are object keys taken from a request body or from an object or deepObject query parameter, which appear in the JSON Schema error's instance path when a schema rejects them (for example under additionalProperties: false), and the raw Content-Type header, reflected in unsupported-media-type errors when it fails to parse. Because browsers send Accept: text/html on ordinary top-level navigation, a crafted GET link is sufficient to trigger the error page; no form submission, custom Content-Type, or attacker-controlled script on the victim's side is required. A payload such as filter[ ]=x terminates the enclosing markup and the injected script executes in the origin of the application using oaskit, giving it access to that origin's cookies, session, and same-origin responses. Both HTML error rendering and the vulnerable handler are enabled by default: Oaskit.Plugs.ValidateRequest defaults :html_errors to true and :error_handler to Oaskit.ErrorHandler.Default, so applications following the documented usage are affected without any opt-in. This issue affects oaskit: from 0.1.0 before 0.14.1.
Weakness: CWE-79
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- Disable HTML error rendering so that validation failures are returned as JSON only: plug Oaskit.Plugs.ValidateRequest, html_errors: false This prevents the vulnerable HTML page from being rendered at all, on any oaskit version. Alternatively, configure a custom :error_handler that does not emit HTML built from request-derived values. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| lud | oaskit | from 0.1.0 before 0.14.1 | 0.14.1 | NIST NVD |
| lud | oaskit | from 0.1.0 before 0.14.1 | 0.14.1 | CVE Program |
| lud | oaskit | from 552de8ca0ff60617bea58bcafa451892d61a161c before b70c6b2eaf0b11bdd0bbb21b8a87dbb3d46918a1 | b70c6b2eaf0b11bdd0bbb21b8a87dbb3d46918a1 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by NVD (reference tagged Patch)
Vendor guidance and references
- EEF CNA record for CVE-2026-66296 (opens in a new tab)patch, related, third party advisory
- Fix commit b70c6b2 in lud/oaskit (opens in a new tab)patch
- https://github.com/lud/oaskit/security/advisories/GHSA-h7xw-x8wr-xpcc (opens in a new tab)vendor-advisory, related
- OSV record EEF-CVE-2026-66296 (opens in a new tab)patch, related, third party advisory
- Introducing commit 552de8c in lud/oaskit (opens in a new tab)related