How severe is CVE-2020-1940?

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

Which packages are affected by CVE-2020-1940?

CVE-2020-1940 affects the following packages: org.apache.jackrabbit:oak-core (Maven), org.apache.jackrabbit:oak-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-1940?

Update org.apache.jackrabbit:oak-core to 1.24.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1940 is resolved across your whole dependency graph.

How do I detect CVE-2020-1940 in my Maven dependencies?

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

How do I mitigate CVE-2020-1940 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-2020-1940 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-1940 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-1940?

CVE-2020-1940 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 91th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-1940?

CVE-2020-1940 is classified as CWE-212 (CWE-212). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-1940 published, and has it been updated?

CVE-2020-1940 was published on January 28, 2020 and was last updated on July 8, 2026. 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-2020-1940 — oak-core

HIGH

CVE-2020-1940 is a high-severity (CVSS 7.5) CWE-212 vulnerability in org.apache.jackrabbit:oak-core. A fix is available for org.apache.jackrabbit:oak-core — see the affected versions and patch details below.

Improper Removal of Sensitive Information Before Storage or Transfer in Apache Jackrabbit Oak

Also known asGHSA-3h68-wvv6-8r5h

Published

Jan 28, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-1940 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.apache.jackrabbit:oak-core☕org.apache.jackrabbit:oak-core

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 optional initial password change and password expiration features present in Apache Jackrabbit Oak 1.2.0 to 1.22.0 are prone to a sensitive information disclosure vulnerability. The code mandates the changed password to be passed as an additional attribute to the credentials object but does not remove it upon processing during the first phase of the authentication. In combination with additional, independent authentication mechanisms, this may lead to the new password being disclosed.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.jackrabbit:oak-core`	≥ 1.12.0&&< 1.24.0	1.24.0`org.apache.jackrabbit:oak-core:1.24.0`
☕Maven	`org.apache.jackrabbit:oak-core`	≥ 1.10.0&&< 1.10.8	1.10.8`org.apache.jackrabbit:oak-core:1.10.8`

Affected Products

1 product · 1 configurations

Application

jackrabbit oakapache

≥ 1.2.0 && ≤ 1.22.0

range

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.jackrabbit:oak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.jackrabbit:oak-core to 1.24.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1940 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

O3 Security · Impact-Aware SCA

Is CVE-2020-1940 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works