GHSA-px9g-8hgv-jvg2 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in kamadak-exif. A fix is available for kamadak-exif — see the affected versions and patch details below.
kamadak-exif vulnerable to Infinite loop when parsing PNG files
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-px9g-8hgv-jvg2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
kamadak-exifReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Reader::read_from_container can cause an infinite loop when a crafted PNG file is given.
Patches
Version 0.5.3 includes the fix.
Workarounds
No workaround is available. Applications that do not pass files with the PNG signature to Reader::read_from_container are not affected.
References
- https://github.com/kamadak/exif-rs/security/advisories/GHSA-px9g-8hgv-jvg2
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21235
For more information
If you have any questions or comments about this advisory:
- Open an issue in github.com/kamadak/exif-rs
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | kamadak-exif | ≥ 0.5.2&&< 0.5.3 | 0.5.3cargo update -p kamadak-exif --precise 0.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kamadak-exif, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kamadak-exif to 0.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-px9g-8hgv-jvg2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-px9g-8hgv-jvg2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-px9g-8hgv-jvg2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-px9g-8hgv-jvg2 in your dependencies?
O3 Security finds GHSA-px9g-8hgv-jvg2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.