CVE-2013-1910: yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly

This week

CRITICAL 9.8REMOTEWATCHLISTDOWNGRADEMITIGATE

CVE-2013-1910 is a critical-severity flaw (CVSS 9.8) affecting yum, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.6% (top 15%)
CISA exploited list	No
Weakness	CWE-20
Published	2019-10-31
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: baseurl · debian

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

Am I affected?

Timeline

2019-10-31 19:15 UTCPublished CVE record published
2026-06-16 23:52 UTCUpdated Record last modified

baseurl yum DOWNGRADE

Affected: 3.4.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.4.3

1. Check installed version

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

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

apt-cache madison yum sudo apt install yum=<VERSION_BEFORE_3.4.3> sudo apt-mark hold yum

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

dnf --showduplicates list yum sudo dnf downgrade yum-<VERSION_BEFORE_3.4.3> sudo dnf versionlock add yum

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.

debian debian linux MITIGATE

Affected: 8.0 · 9.0 · 10.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2013-1910?

yum: downgrade or apply the listed mitigation; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2013-1910 being exploited?

CVE-2013-1910 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-2013-1910 affect?

CVE-2013-1910 affects yum, debian linux. Severity is critical (CVSS 9.8). yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.

How urgent is CVE-2013-1910?

Priority 66/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities

References

← Back to latest CVEs