CVE-2026-91928 Apache Sling XSS: Sanitizer bypass, uncontrolled resource consumption and failure pf protection mechanisms
Medium 6.1
Published
Updated
Check this codebase for CVE-2026-91928 and fix it if it is affected.
What it is: CVE-2026-91928 is a medium-severity vulnerability in Apache Sling XSS, published on 23 Sep 2026.
Exploitation: There is no known exploitation of CVE-2026-91928 in the wild and no public exploit code.
Affected product: Apache Sling XSS. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-91928/ (Markdown: https://insights.sbomify.com/CVE-2026-91928/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-91928?
CVE-2026-91928 is a medium-severity vulnerability in Apache Sling XSS, published on 23 Sep 2026.
Official description
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Apache Sling XSS.
This issue affects Apache Sling XSS: before 2.4.12.
Users are recommended to upgrade to version 2.4.12, which fixes the issue.
Weakness: CWE-79
Which versions are affected by CVE-2026-91928?
It affects 1 product.
Products include Apache Sling Xss Protection Api.
How do I fix CVE-2026-91928?
No fix has been published for CVE-2026-91928 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-91928 being exploited?
There is no known exploitation of CVE-2026-91928 in the wild and no public exploit code.
Other vulnerabilities in Apache Sling XSS
- CVE-2026-73192 Apache Sling XSS: XSS possible through XSSAPI.getValidHref()
- CVE-2026-91852 Apache Sling XSS: CWE-79 multiple raw-string break-outs and ReDOS in XSSImpl
- CVE-2026-91999 Apache Sling XSS: Improper escaping in the XSS Webconsole plugin
- CVE-2026-92001 Apache Sling XSS: Missing parser resource limits
- CVE-2017-15717 Cross-site Scripting in Apache Sling XSS Protection API
Sources
Also known as GHSA-rrc3-fm2q-6j2c.