How severe is CVE-2019-10214?

CVE-2019-10214 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10214?

CVE-2019-10214 affects the following packages: github.com/containers/image (Go). Ecosystems affected: Go.

How do I fix CVE-2019-10214?

Update github.com/containers/image to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10214 is resolved across your whole dependency graph.

How do I detect CVE-2019-10214 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-10214 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-10214 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10214 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-10214?

CVE-2019-10214 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10214?

CVE-2019-10214 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-10214 published, and has it been updated?

CVE-2019-10214 was published on November 25, 2019 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2019-10214 — image

MEDIUMFix: containers/image#655

CVE-2019-10214 is a medium-severity (CVSS 5.9) CWE-522 vulnerability in github.com/containers/image. A fix is available for github.com/containers/image — see the affected versions and patch details below.

containers/image library Insufficiently Protects Credentials

Also known asGHSA-85p9-j7c9-v4grGO-2021-0081

Published

Nov 25, 2019

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-10214 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹github.com/containers/image

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The containers/image library used by the container tools Podman, Buildah, and Skopeo in Red Hat Enterprise Linux version 8 and CRI-O in OpenShift Container Platform, does not enforce TLS connections to the container registry authorization service. An attacker could use this vulnerability to launch a MiTM attack and steal login credentials or bearer tokens.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containers/image`	all versions	3.0.0`go get github.com/containers/image@v3.0.0`

Affected Products

6 products · 6 configurations

Application

buildahbuildah_project

all

Application

libpodlibpod_project

all

leapopensuse

1 version

15.1

enterprise linuxredhat

1 version

8.0

Application

openshift container platformredhat

1 version

4.1

Application

skopeoskopeo_project

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/image to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10214 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`container-tools:rhel8-8010020190927090915.4985cc55`	RHSA-2019:3403
Red Hat Enterprise Linux 8	`container-tools:1.0-8010020190927091243.4985cc55`	RHSA-2019:3494
Red Hat OpenShift Container Platform 3.10	`atomic-openshift-0:3.10.175-1.git.0.f9f0e81.el7`	RHSA-2019:2989
Red Hat OpenShift Container Platform 3.11	`cri-o-0:1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7`	RHSA-2019:2817
Red Hat OpenShift Container Platform 3.9	`cri-o-0:1.9.16-5.git858756d.el7`	RHSA-2019:3812
Red Hat OpenShift Container Platform 4.1	`cri-o-0:1.13.11-0.4.dev.rhaos4.1.git9cb8f2f.el7`	RHSA-2019:2825
Red Hat OpenShift Container Platform 4.1	`openshift4/ose-docker-builder:v4.1.20-201910102034`	RHSA-2019:3007

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-10214 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-522CWE-522

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

image

5.0/10

Code-Review8/10

Maintained0/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Nov 25, 2019

Last updated

Jul 8, 2026

Identifiers

CVE-2019-10214

GHSA-85p9-j7c9-v4gr

GO-2021-0081

References

Advisorylists.opensuse.org Advisorylists.opensuse.org Advisorynvd.nist.gov Fixbugzilla.redhat.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webbugzilla.redhat.com Webpkg.go.dev Packagegithub.com

Related vulnerabilities

Also affects image

This CVE is medium severity; 1 of 1 other CVE affecting image is rated as high or higher (top: high).

CVE-2024-3727

Same weakness: CWE-522

This CVE is medium severity; 6 of 7 other CVEs with CWE-522 are rated as high or higher (top: high).

CVE-2026-76839CVE-2026-85717CVE-2026-76846CVE-2026-85720CVE-2026-88013CVE-2026-59158CVE-2026-71494Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2019-10214 — image

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-10214 in your dependencies?