How severe is CVE-2022-30126?

CVE-2022-30126 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-30126?

CVE-2022-30126 affects the following packages: org.apache.tika:tika-core (Maven), org.apache.tika:tika-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-30126?

Update org.apache.tika:tika-core to 1.28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30126 is resolved across your whole dependency graph.

How do I detect CVE-2022-30126 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-30126 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-30126 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-2022-30126?

CVE-2022-30126 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th 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.

When was CVE-2022-30126 published, and has it been updated?

CVE-2022-30126 was published on May 16, 2022 and was last updated on October 28, 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

MEDIUM severity

CVE-2022-30126 — tika-core

MEDIUMFix: apache/tika@83b0de4

CVE-2022-30126 is a medium-severity (CVSS 5.5) vulnerability in org.apache.tika:tika-core. A fix is available for org.apache.tika:tika-core — see the affected versions and patch details below.

Apache Tika Regular Expression Denial of Service in Standards Extractor

Also known asGHSA-rpjm-422r-95mh

Published

May 16, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% 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

2 pkgs affected

☕org.apache.tika:tika-core☕org.apache.tika:tika-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

This was originally fixed in 1.28.2 and 2.4.0. While the fix in version 2.4.0 was complete, the fix for the 1.x branch wasn't incorporated until version 1.28.3. Please see GHSA-qw3f-w4pf-jh5f for more information.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tika:tika-core`	≥ 1.17&&< 1.28.2	1.28.2`org.apache.tika:tika-core:1.28.2`
☕Maven	`org.apache.tika:tika-core`	≥ 2.0.0&&< 2.4.0	2.4.0`org.apache.tika:tika-core:2.4.0`

Affected Products

2 products · 7 configurations

Application

tikaapache

≥ 2.0.0 && < 2.4.0

range

Application

primavera unifieroracle

≥ 17.7 && ≤ 17.12

4 versions

18.819.1220.1221.12

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.tika:tika-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tika:tika-core to 1.28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30126 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat Fuse 7.11	`tika-core`	RHSA-2022:5532

Frequently Asked Questions

In Apache Tika, a regular expression in our StandardsText class, used by the StandardsExtractingContentHandler could lead to a denial of service caused by backtracking on a specially crafted file. This only affects users who are running the StandardsExtractingContentHandler, which is a non-standard handler. This was originally fixed in 1.28.2 and 2.4.0. While the fix in version 2.4.0 was complete, the fix for the 1.x branch wasn't incorporated until version 1.28.3. Please see GHSA-qw3f-w4pf-jh5f for more information.

O3 Security · Impact-Aware SCA

Is CVE-2022-30126 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works