Vulert records 2 vulnerabilities for exif in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does exif have?

2 vulnerabilities are recorded for exif in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new exif vulnerabilities disclosed?

0 vulnerabilities were recorded for exif in the last 12 months, and the oldest entry in this database dates to 13 Jul 2012. 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 exif 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 exif for upcoming vulnerabilities?

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

Vulnerability Database · Debian · Package report

exif: vulnerability history, versions and safety

exif is a package in the Debian ecosystem. Vulert records 2 vulnerabilities for it across 3 releases, from Jul 2012 to Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded U2

1 with no fix published

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

See the unfixed vulnerabilities →

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all exif vulnerabilities

Vulert verdict on exif i

Updated on 23 Oct 2026

Careful: one of the 2 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 2 vulnerabilities on record across 8 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 2 over 8 years · 0 in the last year i
Latest disclosure 14 Apr 2021 i
Highest CVSS 5.5 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert holds for exif, 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.

Version	Vulert vulnerabilities	Fix published	Details
0.6.22-4	U1	No	Details →
0.6.22-3	U1	No	Details →
0.6.22-2	U1	No	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2012 1
2021 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for exif

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
NULL Pointer Dereference in exif Command Line Tool	5.5 medium	No fix published	14 Apr 2021
Integer Overflow Vulnerability in exif Package Leading to Denial of Service	N/A unrated	0.6.20-2	13 Jul 2012

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