CVE-2021-3496: A heap-based buffer overflow was found in jhead in version 3.06 in Get16u() in exif.c when processing a crafte

This month

HIGH 7.8DOWNGRADE

CVE-2021-3496 is a high-severity flaw (CVSS 7.8) affecting jhead. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A heap-based buffer overflow was found in jhead in version 3.06 in Get16u() in exif.c when processing a crafted file.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-119, CWE-787
Published	2021-04-22
Last modified	2026-06-17

Publisher (CNA): Fedora Project · Vendor: jhead project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-04-22 19:15 UTCPublished CVE record published
2026-06-17 04:05 UTCUpdated Record last modified

jhead project jhead DOWNGRADE

Affected: 3.06

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.06

1. Check installed version

apt-cache policy jhead || rpm -q jhead || jhead --version

2. No fixed release: DOWNGRADE to a release before 3.06 (Debian / Ubuntu)

apt-cache madison jhead sudo apt install jhead=<VERSION_BEFORE_3.06> sudo apt-mark hold jhead

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jhead sudo dnf downgrade jhead-<VERSION_BEFORE_3.06> sudo dnf versionlock add jhead

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-3496?

jhead: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2021-3496 being exploited?

CVE-2021-3496 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-3496 affect?

CVE-2021-3496 affects jhead. Severity is high (CVSS 7.8). A heap-based buffer overflow was found in jhead in version 3.06 in Get16u() in exif.c when processing a crafted file.

How urgent is CVE-2021-3496?

Priority 48/100. High severity; Public exploit reference

Related CVEs

CVE-2025-44906 HIGH 7.8 DOWNGRADE jhead v3.08 was discovered to contain a heap-use-after-free via the ProcessFile function at jhead.c.
CVE-2022-41751 HIGH 7.8 DOWNGRADE MITIGATE Jhead 3.06.0.1 allows attackers to execute arbitrary OS commands by placing them in a JPEG filename and then u
CVE-2022-28550 CRITICAL 9.8 DOWNGRADE Matthias-Wandel/jhead jhead 3.06 is vulnerable to Buffer Overflow via shellescape(), jhead.c, jhead
CVE-2021-34055 HIGH 7.8 DOWNGRADE MITIGATE jhead 3.06 is vulnerable to Buffer Overflow via exif.c in function Put16u.
CVE-2021-28278 HIGH 7.8 DOWNGRADE A Heap-based Buffer Overflow vulnerability exists in jhead 3.04 and 3.05 via the RemoveSectionType function in

References

← Back to latest CVEs