Cross-site request forgery (CSRF) vulnerability in the CSRF content-type check in Jackrabbit-Webdav in Apache Jackrabbit 2.4.x before 2.4.6,
Cross-site request forgery (CSRF) vulnerability in the CSRF content-type check in Jackrabbit-Webdav in Apache Jackrabbit 2.4.x before 2.4.6, 2.6.x before 2.6.6, 2.8.x before 2.8.3, 2.10.x before 2.10.4, 2.12.x before 2.12.4, and 2.13.x before 2.13.3 allows remote attackers to hijack the authentication of unspecified victims for requests that create a resource via an HTTP POST request with a (1) missing or (2) crafted Content-Type header.
- Published
- Sep 21, 2016
- Updated
- Jun 16, 2026
- EPSS
- 2.3% · 83th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| apache | jackrabbit | cpe:2.3:a:apache:jackrabbit |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache jackrabbit2.10.0
- apache jackrabbit2.10.1
- apache jackrabbit2.10.2
- apache jackrabbit2.10.3
- apache jackrabbit2.12.0
- apache jackrabbit2.12.1
- apache jackrabbit2.12.2
- apache jackrabbit2.12.3
- apache jackrabbit2.13.0
- apache jackrabbit2.13.1
- apache jackrabbit2.13.2
- apache jackrabbit2.4.0
- apache jackrabbit2.4.1
- apache jackrabbit2.4.2
- apache jackrabbit2.4.3
- apache jackrabbit2.4.4
- apache jackrabbit2.4.5
- apache jackrabbit2.6.0
- apache jackrabbit2.6.1
- apache jackrabbit2.6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | jackrabbit | before 2.12.4-1 | 2.12.4-1 |
| Debian:7 | jackrabbit | before 2.3.6-1+deb7u2 | 2.3.6-1+deb7u2 |
| Debian:8 | jackrabbit | before 2.3.6-1+deb8u2 | 2.3.6-1+deb8u2 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.10.0 · before 2.10.4 | 2.10.4 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.12.0 · before 2.12.4 | 2.12.4 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.13.0 · before 2.13.3 | 2.13.3 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.4.0 · before 2.4.6 | 2.4.6 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.6.0 · before 2.6.6 | 2.6.6 |
| Maven | org.apache.jackrabbit:jackrabbit-webdav | from 2.8.0 · before 2.8.3 | 2.8.3 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-1833XML external entity (XXE) vulnerability in Apache Jackrabbit before 2.0.6, 2.2.x before 2.2.14, 2.4.x before 2.4.6, 2.6.x before 2.6.6, 2.8.42Plan
- CVE-2023-37895Apache Jackrabbit RMI access can lead to RCE40Plan
- CVE-2025-53689Apache Jackrabbit: XXE vulnerability in jackrabbit-spi-commons35Monitor
- CVE-2025-58782Apache Jackrabbit Core, Apache Jackrabbit JCR Commons: JNDI injection risk with JndiRepositoryFactory26Monitor
- CVE-2009-0026Multiple cross-site scripting (XSS) vulnerabilities in Apache Jackrabbit before 1.5.2 allow remote attackers to inject arbitrary web script 25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:jackrabbit | 2.12.4-1 · Debian:12 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.10.4 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.12.4 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.13.3 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.4.6 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.6.6 | Package registry (OSV) |
| Maven:org.apache.jackrabbit:jackrabbit-webdav | 2.8.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.debian.org/security/2016/dsa-3679
- www.openwall.com/lists/oss-security/2016/09/14/6
- www.securityfocus.com/bid/92966
- issues.apache.org/jira/browse/JCR-4009
Vendor advisories and official records. Exploit/PoC links are deliberately left out.