CVE-2019-11253

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 86% probability of exploitation within the next 30 days (top 0.6% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 26%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.

CVSS v3
7.5
EG Score
9.0(high)
EPSS
97.7%
KEV
Not listed

Published

October 17, 2019

Last Modified

February 24, 2026

References (12)

Vendor Advisories for CVE-2019-11253(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhosp-rhel8-tech-preview/osp-director-operator:1.2.3-22022-05-11redhat
redhatservicemesh-grafana-0:6.2.2-38.el82020-07-07redhat
redhatservicemesh-cni-0:1.0.11-1.el82020-07-07redhat
redhatservicemesh-prometheus-0:2.7.2-36.el82020-07-07redhat
redhatservicemesh-cni-0:1.1.4-2.el82020-07-01redhat
redhatservicemesh-grafana-0:6.4.3-11.el82020-07-01redhat
redhatservicemesh-operator-0:1.1.4-3.el82020-07-01redhat
redhatatomic-openshift-0:3.11.154-1.git.0.7a097ad.el72019-11-18redhat
redhatatomic-openshift-0:3.9.102-1.git.0.6411f52.el72019-11-07redhat
redhatservicemesh-proxy-0:1.0.2-3.el82019-11-07redhat
redhatatomic-openshift-0:3.10.181-1.git.0.3ab4b3d.el72019-10-29redhat
redhatopenshift-0:4.1.20-201910101746.git.0.a80aad5.el72019-10-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
k8s.io/kubernetes—1.16.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:42 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-02 18:05 UTCOSV refresh
  10. 2026-07-02 16:56 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-07-01 15:03 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-28 14:04 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:53 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 35 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-18 17:50 UTCEPSS rescore
  6. 2026-06-17 17:50 UTCEPSS rescore
  7. 2026-06-16 17:50 UTCEPSS rescore
  8. 2026-06-15 17:45 UTCEPSS rescore
  9. 2026-06-14 23:15 UTCEPSS rescore
  10. 2026-06-14 23:15 UTCEPSS rescore
  11. 2026-06-14 16:13 UTCOSV refresh
  12. 2026-06-13 22:58 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-10 22:16 UTCEPSS rescore
  15. 2026-06-10 13:19 UTCEPSS rescore
  16. 2026-06-08 14:15 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-04 13:10 UTCEPSS rescore
  24. 2026-06-01 13:50 UTCEPSS rescore
  25. 2026-06-01 13:50 UTCEPSS rescore
  26. 2026-05-31 22:29 UTCEPSS rescore
  27. 2026-05-31 22:29 UTCEPSS rescore
  28. 2026-05-29 13:42 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-27 12:48 UTCEG score recompute
  31. 2026-05-27 12:48 UTCVendor advisory
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-26 13:42 UTCEPSS rescore
  34. 2026-05-26 07:17 UTCEPSS rescore
  35. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2019/CVE-2019-11253.yaml
    First seen Jan 1, 2019

    Kubernetes API Server - YAML Parsing DoS (Billion Laughs)

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-11253?
CVE-2019-11253 is a high vulnerability published on October 17, 2019. Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming…
When was CVE-2019-11253 disclosed?
CVE-2019-11253 was first published in the National Vulnerability Database on October 17, 2019, with the most recent update on February 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-11253 actively exploited?
CVE-2019-11253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-11253?
CVE-2019-11253 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-11253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-11253, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-11253

Explore →

Is Your Infrastructure Affected by CVE-2019-11253?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs