How severe is CVE-2022-24613?

CVE-2022-24613 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-24613?

CVE-2022-24613 affects the following packages: com.drewnoakes:metadata-extractor (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-24613?

Update com.drewnoakes:metadata-extractor to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24613 is resolved across your whole dependency graph.

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

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

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

Yes. There are 1 known exploit references for CVE-2022-24613, including 1 in-the-wild exploitation observed on GitHub and other sources. 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-2022-24613?

CVE-2022-24613 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th 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-2022-24613?

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

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

CVE-2022-24613 was published on February 24, 2022 and was last updated on August 12, 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-24613 — metadata-extractor

MEDIUM

CVE-2022-24613 is a medium-severity (CVSS 5.5) CWE-755 vulnerability in com.drewnoakes:metadata-extractor. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.drewnoakes:metadata-extractor — see the affected versions and patch details below.

Improper Handling of Exceptional Conditions inn metadata-extractor

Also known asGHSA-p5pg-wm9q-8v6r

Published

Feb 24, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-24613 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

1 pkg affected

☕com.drewnoakes:metadata-extractor

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

metadata-extractor up to 2.16.0 can throw various uncaught exceptions while parsing a specially crafted JPEG file, which could result in an application crash. This could be used to mount a denial of service attack against services that use metadata-extractor library.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.drewnoakes:metadata-extractor`	all versions	2.18.0`com.drewnoakes:metadata-extractor:2.18.0`

Affected Products

1 product · 1 configurations

Application

metadata-extractormetadata-extractor_project

< 2.18.0

range

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.

metadata-extractor up to 2.16.0 can throw various uncaught exceptions wh…

github.comNVDMar 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.drewnoakes:metadata-extractor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.drewnoakes:metadata-extractor to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24613 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-24613 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-755CWE-755

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 24, 2022

First exploit

Mar 2, 2022

6 days after disclosure — rapid exploitation

Last updated

Aug 12, 2026

Identifiers

CVE-2022-24613

GHSA-p5pg-wm9q-8v6r

References

Advisorygithub.com Advisorynvd.nist.gov Reportgithub.com Packagegithub.com

Related vulnerabilities

Also affects metadata-extractor

This CVE is medium severity; 1 of 1 other CVE affecting metadata-extractor is rated as high or higher (top: high).

CVE-2022-24614

Same weakness: CWE-755

This CVE is medium severity; 7 of 7 other CVEs with CWE-755 are rated as high or higher (top: high).

CVE-2026-81516CVE-2026-81515CVE-2026-59162GHSA-jwjp-4649-v8jpGHSA-pfvm-w89x-94jwCVE-2026-52856CVE-2026-54632Browse all CWE-755

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026

CVE-2022-24613 — metadata-extractor

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-2022-24613 in your dependencies?