Skip to main content
VulnerabilityPublished

CVE-2026-103866: Apache Sling Engine · Interpretation Conflict

Affects Apache Sling EngineSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 3.0.4 soon.

Data as of 5 Nov 2026, 13:04 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.0.4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Apache Sling Engine to 3.0.4.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Sling EngineAffected
  • <3.0.4
Fixed in
  • 3.0.4

AI-suggested

Users should upgrade Apache Sling Engine to version 3.0.4 or later, where this vulnerability is fixed. No other mitigations are indicated.

Description

Apache Sling Engine versions before 3.0.4 contain an HTTP request/response smuggling vulnerability due to inconsistent interpretation of HTTP requests. The engine's query and form parser accepts non-standard percent-escapes and incorrect character sets, continuing request processing despite these errors. This issue is fixed in version 3.0.4.

References

Community reviews

Loading reviews…