CVE-2026-0319

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-101633 (ENISA EUVD) · GHSA-jr9m-vg87-w232 (GitHub Security Advisories)Source: ENISA EUVD

4.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.9Exploit: None knownExposed services: Not assessed

Upgrade to 12.2.4 or later (from the CVE record's solution, Palo Alto Networks, Inc.) — apply it.

An improper input handling vulnerability in the GlobalProtect™ gateway of Palo Alto Networks PAN-OS software enables an authenticated user to establish a GlobalProtect session using the identity of another user.

Cloud NGFW and Panorama are not affected by this vulnerability.

CVSS
4.9
EG Score
4.9MEDIUMmedium confidence
EG Risk
22
EG Risk 22/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)
Severity49% × 45%
Impact severity (EG Severity): CVSS 4.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: Upgrade to 12.2.4 or later (from the CVE record's solution, Palo Alto Networks, Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (4.9): severity, escalated by confirmed exploitation. This CVE's 4.9 is its impact severity (EG Severity), not escalated.

EG Severity
4.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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).

Upgrade to 12.2.4 or later (from the CVE record's solution, Palo Alto Networks, Inc.). Apply it within your standard update timelines.

Exploitation none (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)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 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

Published

October 14, 2026

Last Modified

November 10, 2026

Advisory Details (1)

Auto-updated Oct 14, 2026
Fix named in the CVE record's solution (Palo Alto Networks, Inc.).
Web page

CVE-2026-0319 PAN-OS: Improper Input Handling Vulnerability

https://security.paloaltonetworks.com/CVE-2026-0319

Vendor Advisories for CVE-2026-0319(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-11-11 05:47 UTCEchelonGraph re-scored
  5. 2026-11-11 05:47 UTCGHSA enrichmentGHSA-jr9m-vg87-w232 · GitHub severity MODERATE
  6. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-10 13:31 UTCEchelonGraph re-scored
  8. 2026-11-10 13:31 UTCGHSA enrichmentGHSA-jr9m-vg87-w232 · GitHub severity MODERATE
  9. 2026-11-10 12:47 UTCEchelonGraph re-scored
  10. 2026-11-10 12:47 UTCGHSA enrichmentGHSA-jr9m-vg87-w232 · GitHub severity MODERATE
  11. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-11-04 00:23 UTCEchelonGraph re-scored
  18. 2026-11-04 00:23 UTCGHSA enrichmentGHSA-jr9m-vg87-w232 · GitHub severity MODERATE
  19. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-29 14:46 UTCEchelonGraph re-scored
  25. 2026-10-29 14:46 UTCGHSA enrichmentGHSA-jr9m-vg87-w232
Show 27 more
  1. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-25 15:58 UTCEchelonGraph re-scored
  6. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-23 10:28 UTCEchelonGraph re-scored
  9. 2026-10-23 10:28 UTCGHSA enrichmentGHSA-jr9m-vg87-w232
  10. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-18 05:12 UTCEchelonGraph re-scored
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-15 19:39 UTCEchelonGraph re-scored
  19. 2026-10-15 19:38 UTCGHSA enrichmentGHSA-jr9m-vg87-w232
  20. 2026-10-15 19:06 UTCEchelonGraph re-scored
  21. 2026-10-15 19:05 UTCGHSA enrichmentGHSA-jr9m-vg87-w232
  22. 2026-10-15 16:48 UTCEchelonGraph re-scored
  23. 2026-10-15 16:48 UTCGHSA enrichmentGHSA-jr9m-vg87-w232
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-14 21:32 UTCEchelonGraph re-scored
  26. 2026-10-14 20:26 UTCEchelonGraph re-scoredFirst assessed: 4.9 MEDIUM
  27. 2026-10-14 20:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-0319?
CVE-2026-0319 is a medium-severity vulnerability; its CVE record was published on October 14, 2026. An improper input handling vulnerability in the GlobalProtect™ gateway of Palo Alto Networks PAN-OS software enables an authenticated user to establish a GlobalProtect session using the identity of another user. Cloud NGFW and Panorama are not affected by this vulnerability.
When was CVE-2026-0319 made public?
CVE-2026-0319 was made public on October 14, 2026: that is the date its CVE record's CNA, Palo Alto Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-0319 actively exploited?
CVE-2026-0319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0319?
CVE-2026-0319 has a CVSS base score of 4.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-0319?
The CVE record's solution for CVE-2026-0319, written by its CNA Palo Alto Networks, Inc., names the fix: "Upgrade to 12.2.4 or later." The vendor advisories EchelonGraph has for CVE-2026-0319 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0319

Explore →

Is Your Infrastructure Affected by CVE-2026-0319?

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