CVE-2026-103864: Apache Sling Engine improper output neutralization in logs

CVE-2026-103864 · Severity: info · Published 2026-11-05

Apache Sling Engine, a framework for building web applications, does not properly neutralize output written to logs. An attacker with the ability to influence log content could potentially inject malicious data into logs, which may be exploited if those logs are later displayed in a web interface or processed by other tools without proper sanitization.

Technologies: Apache Sling Engine. Vendors: Apache.

Quick answers

Is CVE-2026-103864 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-103864 being exploited in the wild.
How severe is CVE-2026-103864?
Informational severity, published 5 November 2026.
Which products and versions are affected?
Apache Sling Engine before 3.0.4.
Is there a fix for CVE-2026-103864?
Yes: fixed in 3.0.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-103864 attacked?
It is in a software library.
Am I affected by CVE-2026-103864?
Check whether you run Apache Sling Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 3.0.4

Technical details

The vulnerability involves improper output neutralization (CWE-117) for logs in Apache Sling Engine. Untrusted data written to application logs is not properly escaped or neutralized, allowing injection attacks. The vulnerability affects versions before 3.0.4 and can be exploited by attackers who can control input that reaches the logging subsystem.

Affected products

  • Apache Sling Engine before 3.0.4

Timeline

  • 2026-11-05: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.