CVE-2026-103863 · Package
NO FIX YET · SEE WHAT TO DO
Apache Sling Engine lets an included component change Content-Type, charset and redirect settings in ways that skip its header and content-type checks. An attacker can therefore store script in a page that runs in other users' browsers despite the protections being enabled.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications running Apache Sling Engine before 3.0.4 that render content from included components. Sites that do not use Sling or that run a patched version can skip it. The sources do not say which configurations are most exposed.
Not affected if patched-version
Who cares apache-sling, cms, java, stored-xss
org.apache.sling.engine).3.0.4 or later.Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Apache Sling Engine. Content-Type, charset, and redirect changes from an included component evade the protectheaders / checkcontenttype enforcement through setHeader(), repeated calls to setContentType(), the charset APIs, Servlet 6.1 redirect overloads, and stale config - enabling stored XSS despite enabled protections.
This issue affects Apache Sling Engine before 3.0.4.
Users are recommended to upgrade to version 3.0.4, which fixes the issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.