Cross-site scripting via incomplete context-aware sanitization
Published Sep 23, 2026 · Updated Sep 23, 2026
Cross-site scripting in Apache Sling XSS Protection before 2.4.12 allows attackers to execute script through crafted content. XSSAPIImpl accepts raw-text terminators in comments, preserves script-breaking characters in JSON, and permits quote or markup breakouts in style tokens. Exploitation requires a consuming Sling application to pass attacker-controlled values to an affected API and embed its output in HTML viewed by a victim.
Summary
What happened
Cross-site scripting in Apache Sling XSS Protection before 2.4.12 allows attackers to execute script through crafted content. XSSAPIImpl accepts raw-text terminators in comments, preserves script-breaking characters in JSON, and permits quote or markup breakouts in style tokens. Exploitation requires a consuming Sling application to pass attacker-controlled values to an affected API and embed its output in HTML viewed by a victim.
The record
- CVE
- CVE-2026-91852
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- Apache Software Foundation
- Product
- Apache Sling XSS Protection
- Classifications
- CWE-79, T1059.007
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.4.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started