CVE-2019-13272

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2019-4779 (ENISA EUVD) · GHSA-87j5-gppq-mq6h (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 52%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to create a ptrace relationship, which allows local users to obtain root access by leveraging certain scenarios with a parent-child process relationship, where a parent drops privileges and calls execve (potentially allowing control by an attacker). One contributing factor is an object lifetime issue (which can also cause a panic). Another contributing factor is incorrect marking of a ptrace relationship as privileged, which is exploitable through (for example) Polkit's pkexec helper with PTRACE_TRACEME. NOTE: SELinux deny_ptrace might be a usable workaround in some environments.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
52%
EPSS %ILE
98th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
52% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-13272

Published

July 17, 2019

Last Modified

November 6, 2025

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-5.0.0-1014-aws (5.0.0-1014.16) @ disco2026-11-01ubuntu
ubuntulinux-image-aws-hwe (4.15.0.1047.47) @ xenial2026-11-01ubuntu
ubuntulinux-image-virtual-lts-xenial (4.4.0.159.167) @ xenial2026-11-01ubuntu
ubuntulinux-image-virtual-hwe-16.04 (4.15.0.58.79) @ xenial2026-11-01ubuntu
ubuntulinux-image-virtual (5.0.0.25.26) @ disco2026-11-01ubuntu
redhatkernel-alt-0:4.14.0-115.12.1.el7a2019-09-20redhat
redhatkernel-rt-0:4.18.0-80.7.2.rt9.154.el8_02019-08-07redhat
redhatkernel-0:4.18.0-80.7.2.el8_02019-08-07redhat

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

(8 across 7 ecosystems)
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (65 versions)
  • every version up to 3.16.70-1: fixed in 3.16.70-1
—
linux-4.94.9.110-1~deb8u1, 4.9.144-3.1~deb8u1, 4.9.168-1~deb8u1
  • every version up to 4.9.168-1+deb9u4~deb8u1: fixed in 4.9.168-1+deb9u4~deb8u1
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.37-5
  • every version up to 4.19.37-5+deb10u1: fixed in 4.19.37-5+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.19.37-6: fixed in 4.19.37-6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.19.37-6: fixed in 4.19.37-6
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.19.37-6: fixed in 4.19.37-6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 4.19.37-6: fixed in 4.19.37-6
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.9.107-1 ... 4.9.88-1~bpo8+1 (49 versions)
  • every version up to 4.9.168-1+deb9u4: fixed in 4.9.168-1+deb9u4
—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 27× in last 7d / 189× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,752 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,652 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 22:57 UTCEG score recompute
  2. 2026-11-01 22:57 UTCVendor advisory
  3. 2026-11-01 22:57 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-01 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  5. 2026-10-31 22:14 UTCEG score recompute
  6. 2026-10-31 22:14 UTCVendor advisory
  7. 2026-10-31 22:14 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-31 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  9. 2026-10-30 21:27 UTCEG score recompute
  10. 2026-10-30 21:27 UTCVendor advisory
  11. 2026-10-30 21:27 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-30 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  13. 2026-10-29 20:44 UTCEG score recompute
  14. 2026-10-29 20:44 UTCVendor advisory
  15. 2026-10-29 20:44 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-29 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  17. 2026-10-28 20:00 UTCEG score recompute
  18. 2026-10-28 20:00 UTCVendor advisory
  19. 2026-10-28 20:00 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-28 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  21. 2026-10-27 19:17 UTCEG score recompute
  22. 2026-10-27 19:17 UTCVendor advisory
  23. 2026-10-27 19:17 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-27 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  25. 2026-10-26 18:34 UTCEG score recompute
Show 75 more
  1. 2026-10-26 18:34 UTCVendor advisory
  2. 2026-10-26 18:34 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-26 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  4. 2026-10-25 17:49 UTCEG score recompute
  5. 2026-10-25 17:49 UTCVendor advisory
  6. 2026-10-25 17:49 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-25 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  8. 2026-10-24 17:04 UTCEG score recompute
  9. 2026-10-24 17:04 UTCVendor advisory
  10. 2026-10-24 17:04 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-24 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  12. 2026-10-23 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  13. 2026-10-23 16:21 UTCEG score recompute
  14. 2026-10-23 16:21 UTCVendor advisory
  15. 2026-10-23 16:21 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-22 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  17. 2026-10-22 15:37 UTCEG score recompute
  18. 2026-10-22 15:37 UTCVendor advisory
  19. 2026-10-22 15:36 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-21 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  21. 2026-10-21 14:53 UTCEG score recompute
  22. 2026-10-21 14:53 UTCVendor advisory
  23. 2026-10-21 14:53 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-20 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  25. 2026-10-20 14:10 UTCEG score recompute
  26. 2026-10-20 14:10 UTCVendor advisory
  27. 2026-10-20 14:09 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-19 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  29. 2026-10-19 13:23 UTCEG score recompute
  30. 2026-10-19 13:23 UTCVendor advisory
  31. 2026-10-19 13:23 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-18 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  33. 2026-10-18 12:40 UTCVendor advisory
  34. 2026-10-18 12:40 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-18 09:55 UTCEG score recompute
  36. 2026-10-17 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  37. 2026-10-17 11:55 UTCEG score recompute
  38. 2026-10-17 11:55 UTCVendor advisory
  39. 2026-10-17 11:54 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-10-16 16:31 UTCEPSS rescoreEPSS 52% · 98th percentile
  41. 2026-10-16 11:09 UTCEG score recompute
  42. 2026-10-16 11:09 UTCVendor advisory
  43. 2026-10-16 11:09 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-10-15 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  45. 2026-10-15 10:26 UTCEG score recompute
  46. 2026-10-15 10:26 UTCVendor advisory
  47. 2026-10-15 10:26 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-14 16:28 UTCEPSS rescoreEPSS 52% · 98th percentile
  49. 2026-10-14 09:42 UTCEG score recompute
  50. 2026-10-14 09:42 UTCVendor advisory
  51. 2026-10-14 09:42 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-13 16:27 UTCEPSS rescoreEPSS 52% · 98th percentile
  53. 2026-10-13 08:57 UTCVendor advisory
  54. 2026-10-13 08:57 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-10-12 20:02 UTCEG score recompute
  56. 2026-10-12 08:14 UTCVendor advisory
  57. 2026-10-12 08:14 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-12 03:50 UTCVendor advisory
  59. 2026-10-12 03:50 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-11 23:27 UTCEG score recompute
  61. 2026-10-11 23:27 UTCVendor advisory
  62. 2026-10-11 23:27 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-11 19:03 UTCEG score recompute
  64. 2026-10-11 19:03 UTCVendor advisory
  65. 2026-10-11 19:03 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-10-11 14:41 UTCEG score recompute
  67. 2026-10-11 14:41 UTCVendor advisory
  68. 2026-10-11 14:41 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-10-11 13:41 UTCEPSS rescoreEPSS 52% · 98th percentile
  70. 2026-10-11 10:17 UTCVendor advisory
  71. 2026-10-11 10:17 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-10-11 05:54 UTCVendor advisory
  73. 2026-10-11 05:54 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-11 01:32 UTCVendor advisory
  75. 2026-10-11 01:31 UTCGHSA enrichmentGHSA-87j5-gppq-mq6h · GitHub severity HIGH · GitHub CVSS 7.8

Publicly available exploits

(11 references, 10 shown)

Public exploit code is referenced for this CVE (1 Metasploit module, 4 Exploit-DB entries, 6 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-47543✓ verified
    Published Oct 24, 2019

    Linux Polkit - pkexec helper PTRACE_TRACEME local root (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/local/ptrace_traceme_pkexec_helper✓ verified
    Published Oct 23, 2019

    Linux Polkit pkexec helper PTRACE_TRACEME local root exploit

    Open source ↗
  • Exploit-DBEDB-47133✓ verified
    Published Jul 17, 2019

    Linux - Broken Permission and Object Lifetime Handling for PTRACE_TRACEME

    Open source ↗
  • GitHub PoCjosemlwdf/CVE-2019-13272
    Published Jun 20, 2024

    This is a Python 3 version of this exploit. Hope it works!!!

    Open source ↗
  • GitHub PoCMDS1GNAL/ptrace_scope-CVE-2019-13272-privilege-escalation
    Published Jan 31, 2024

    Es una vulnerabilidad para escalar privilegios en linux.

    Open source ↗
  • Exploit-DBEDB-50541
    Published Nov 23, 2021

    Linux Kernel 5.1.x - 'PTRACE_TRACEME' pkexec Local Privilege Escalation (2)

    Open source ↗
  • GitHub PoCTharana/vulnerability-exploitation
    Published May 12, 2020

    Local Root vulnerability- CVE-2019-13272 / Security Bypass Vulnerability – CVE-2019-14287/Google Android - 'Stagefright' Remote Code Execution - CVE-2015-1538

    Open source ↗
  • GitHub PoConeoy/CVE-2019-13272
    Published Aug 7, 2019

    linux 提权

    Open source ↗
  • GitHub PoCCyc1eC/CVE-2019-13272
    Published Jul 31, 2019

    The exploit for CVE-2019-13272

    Open source ↗
  • GitHub PoCjas502n/CVE-2019-13272
    Published Jul 31, 2019

    Linux 4.10 < 5.1.17 PTRACE_TRACEME local root

    Open source ↗

Frequently asked(6)

What is CVE-2019-13272?
CVE-2019-13272 is a critical-severity vulnerability; its CVE record was published on July 17, 2019. In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to create a ptrace relationship, which allows local users to obtain root access by leveraging certain scenarios with a parent-child process relationship, where a…
When was the CVE record for CVE-2019-13272 published?
The CVE record for CVE-2019-13272 was published on July 17, 2019. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2025; the record at its source may have been updated since.
Is CVE-2019-13272 actively exploited?
Yes. CISA added CVE-2019-13272 to the Known Exploited Vulnerabilities catalog on December 10, 2021, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-13272?
CVE-2019-13272 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2019-13272?
CVE-2019-13272 affects Linux Kernel. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-13272?
A fix for CVE-2019-13272 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2019-13272?

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