Vulnerability · CVE-2023-42447
blurhash: panic on parsing crafted blurhash inputs
Published Sep 19, 2023 · catalog updated Oct 13, 2026 · blurhash: panic on parsing
Check if you run it
No confirmed exploitation is on record for CVE-2023-42447. EPSS is 0.62%. Act only if a listed version of blurhash: panic on parsing is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (blurhash: panic on parsing).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High8.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.62%
- Remediation
- Advisory link
- Affected products
- crates.io blurhash
## Impact The blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input. In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include: - UTF-8 compliant strings containing multi-byte UTF-8 characters ## Patches The patches were released under version 0.2.0, which may require user intervention because of slight API churn.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- crates.io blurhash0.0.0-0 → 0.2.0
How to fix CVE-2023-42447
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-42447. EPSS is 0.62%. Act only if a listed version of blurhash: panic on parsing is installed.
Which versions are affected?
Compare what you have installed with 0.0.0-0 → 0.2.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.62%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 19, 2023 · Catalog
Detected
## Impact The blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input. In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include: - UTF-8 compliant strings containing multi-byte UTF-8 characters ## Patches The patches were released under version 0.2.0, which may require user interv
Oct 13, 2026 · Catalog
Fix available
crates.io blurhash 0.0.0-0 → 0.2.0
Oct 13, 2026 · GitHub Advisory Database
Fix available
blurhash fixed in 0.2.0
Oct 13, 2026 · GitHub Advisory Database
Fix available
blurhash fixed in 0.2.0
Oct 13, 2026 · Catalog
Updated
## Impact The blurhash parsing code may panic due to multiple panic-guarded out-of-bounds accesses on untrusted input. In a typical deployment, this may get triggered by feeding a maliciously crafted blurhashes over the network. These may include: - UTF-8 compliant strings containing multi-byte UTF-8 characters ## Patches The patches were released under version 0.2.0, which may require user interv
Sources
- CVE.orgVulnerability recordCVE-2023-42447
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-42447
30-day exploitation probability 0.6%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-cxvp-82cq-57h2
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2023-0083
blurhash: panic on parsing crafted blurhash inputs
osv.dev
References
Freshness
Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.