CVE-2019-3696

HIGHNVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.4 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2019-13331 (ENISA EUVD) · GHSA-crq2-xjm7-62p8 (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A Improper Limitation of a Pathname to a Restricted Directory vulnerability in the packaging of pcp of SUSE Linux Enterprise High Performance Computing 15-ESPOS, SUSE Linux Enterprise High Performance Computing 15-LTSS, SUSE Linux Enterprise Module for Development Tools 15, SUSE Linux Enterprise Module for Development Tools 15-SP1, SUSE Linux Enterprise Module for Open Buildservice Development Tools 15, SUSE Linux Enterprise Server 15-LTSS, SUSE Linux Enterprise Server for SAP 15, SUSE Linux Enterprise Software Development Kit 12-SP4, SUSE Linux Enterprise Software Development Kit 12-SP5; openSUSE Leap 15.1 allows local user pcp to overwrite arbitrary files with arbitrary content. This issue affects: SUSE Linux Enterprise High Performance Computing 15-ESPOS pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise High Performance Computing 15-LTSS pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise Module for Development Tools 15 pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise Module for Development Tools 15-SP1 pcp versions prior to 4.3.1-3.5.3. SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise Server 15-LTSS pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise Server for SAP 15 pcp versions prior to 3.11.9-5.8.1. SUSE Linux Enterprise Software Development Kit 12-SP4 pcp versions prior to 3.11.9-6.14.1. SUSE Linux Enterprise Software Development Kit 12-SP5 pcp versions prior to 3.11.9-6.14.1. openSUSE Leap 15.1 pcp versions prior to 4.3.1-lp151.2.3.1.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

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

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

Published

March 3, 2020

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Sep 4, 2026
Patch available.
Web page

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=1153921

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpcp-0:4.3.2-12.el72020-09-29redhat
redhatpcp-0:5.0.2-5.el82020-04-28redhat

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.

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× 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 99 of 192 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Same vendor

1 shown

redhat:RHBA-2020:1628

Frequently asked(5)

What is CVE-2019-3696?
CVE-2019-3696 is a high-severity vulnerability; its CVE record was published on March 3, 2020. A Improper Limitation of a Pathname to a Restricted Directory vulnerability in the packaging of pcp of SUSE Linux Enterprise High Performance Computing 15-ESPOS, SUSE Linux Enterprise High Performance Computing 15-LTSS, SUSE Linux Enterprise Module for Development Tools 15, SUSE Linux Enterprise…
When was CVE-2019-3696 made public?
CVE-2019-3696 was made public on February 7, 2020: that is the date its CVE record's CNA, SUSE, gives for when the vulnerability was made public. The CVE record itself was published on March 3, 2020. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2019-3696 actively exploited?
CVE-2019-3696 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-3696?
CVE-2019-3696 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2019-3696?
A fix for CVE-2019-3696 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-3696

Explore →

Is Your Infrastructure Affected by CVE-2019-3696?

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

Book a Demo →Browse All CVEs