How severe is CVE-2016-0956?

CVE-2016-0956 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-0956?

CVE-2016-0956 affects the following packages: org.apache.sling:org.apache.sling.servlets.post (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-0956?

Update org.apache.sling:org.apache.sling.servlets.post to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0956 is resolved across your whole dependency graph.

How do I detect CVE-2016-0956 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.servlets.post, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2016-0956 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2016-0956 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2016-0956, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-0956?

CVE-2016-0956 has an EPSS (Exploit Prediction Scoring System) score of 51.2%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2016-0956?

CVE-2016-0956 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-0956 published, and has it been updated?

CVE-2016-0956 was published on May 14, 2022 and was last updated on February 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2016-0956 — org.apache.sling.servlets…

HIGH

CVE-2016-0956 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.sling:org.apache.sling.servlets.post. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.sling:org.apache.sling.servlets.post — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Sling Servlets Post

Published

May 14, 2022

Updated

Feb 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

51.2%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.sling:org.apache.sling.servlets.post

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The Servlets Post component 2.3.6 in Apache Sling, as used in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, allows remote attackers to obtain sensitive information via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.sling:org.apache.sling.servlets.post`	all versions	2.3.8`org.apache.sling:org.apache.sling.servlets.post:2.3.8`

Affected Products

2 products · 4 configurations

Application

experience manageradobe

3 versions

5.6.16.0.06.1.0

Application

slingapache

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39435webappsmultiple✓ Verified

Apache Sling Framework (Adobe AEM) 2.3.6 - Information Disclosure

by Vulnerability-Lab · Feb 10, 2016

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.servlets.post, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.sling:org.apache.sling.servlets.post to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0956 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

The Servlets Post component 2.3.6 in Apache Sling, as used in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, allows remote attackers to obtain sensitive information via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2016-0956 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

First exploit

Feb 10, 2016

Disclosed

May 14, 2022

Last updated

Feb 20, 2024

Identifiers

CVE-2016-0956

References

Advisorynvd.nist.gov · CVE 2016 0956 Webhelpx.adobe.com · apsb16 05 Webexploit-db.com Webpacketstormsecurity.com · Apache Sling Framework 2.3.6 Information Disclosure Webseclists.org Websecurityfocus.com · threaded

Related vulnerabilities

Also affects org.apache.sling.servlets.post

This CVE is high severity — higher than any of the other 3 CVEs affecting org.apache.sling.servlets.post (highest there: moderate).

CVE-2012-2138CVE-2017-9802CVE-2015-2944

Same weakness: CWE-200

This CVE is high severity; 2 of 5 other CVEs with CWE-200 are rated as high or higher (top: high).

CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 20, 2024

CVE-2016-0956 — org.apache.sling.servlets…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2016-0956 in your dependencies?