VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

exiv2: vulnerability history, versions and safety

exiv2 is a package in the OSS-Fuzz ecosystem. Vulert records 10 vulnerabilities for it across 12 releases, from Mar 2022 to Apr 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H4 M6
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all exiv2 vulnerabilities

Vulert verdict on exiv2 i

Updated on 23 Oct 2026

Careful: one of the 10 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 2 years · 0 in the last year i
  • Latest disclosure 30 Apr 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for exiv2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 7
  • 2023 2
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for exiv2

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Container-overflow in Exiv2::Photoshop::locateIrb N/A medium e715243aa51fa38a89d35ea377d267600217e192 08 Mar 2022
Heap-buffer-overflow in Exiv2::getULong N/A medium d16ca65b01188d28afbe5a52b1495ac0270dd95a 26 Mar 2022
Heap-buffer-overflow in exiv2: std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch> N/A medium 337fe1854ff17f169032e993789a24bbb53579c4 27 Aug 2022
Heap-buffer-overflow in Exiv2::MemIo::read N/A high d3651fdbd352cbaf259f89abf7557da343339378 03 Sep 2022
Heap-buffer-overflow in exiv2: Exiv2::MemIo::read N/A high 0db460c9b0aad040ea1ab0335c3f07d18a0bc4cf 24 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About exiv2

Is exiv2 safe to use?

Vulert records 10 vulnerabilities for exiv2 in OSS-Fuzz: 0 critical, 4 high, 6 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does exiv2 have?

10 vulnerabilities are recorded for exiv2 in the OSS-Fuzz ecosystem: 0 critical, 4 high, 6 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new exiv2 vulnerabilities disclosed?

0 vulnerabilities were recorded for exiv2 in the last 12 months, and the oldest entry in this database dates to 08 Mar 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of exiv2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor exiv2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the exiv2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.