vciy

CVE-2025-0117

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

GlobalProtect App: Local Privilege Escalation (PE) Vulnerability

CVE-2025-01173 of 4 sources documented this
33

rank 33 = 15 + 18 + 0 + 0 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00164  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.1, from the CNA  ·  without this subject the record ranks 15

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 33

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 33

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 33

Hindsight · the state

0.00164EPSSNOT IN KEVas of 2026-10-18
Severity7.1 HIGHreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-03-13, 571 days at 0.00, as of 2026-10-05. arc-rules@v1

Foresight · where to check next

Microsoft 365Apache Tomcat0117

This record is one instance of CWE-807, reliance on untrusted inputs in a security decision. The index holds 130 prior instances of this class, 3 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signal

Which product do you run? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Choose your product above to watch it.

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · passive user interaction · low attack complexity · no attack requirementsreceipt
ImpactComplete integrity loss, with impact on subsequent systemsreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-807 Reliance on Untrusted Inputs in a Security Decisionreceipt
Published consequencesCWE-807: Confidentiality, Access Control, Availability, Other: Bypass Protection Mechanism, Gain Privileges or Assume Identity, Varies by Contextcwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in6.3.3; 6.2.6; 10.2.14; 10.2.13-h5; 10.1.14-h11receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2025-03-14.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2025-03-14receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.1 HIGHreceipt
Exploit probability0.00164 · top 95% of all CVEsreceipt
Assigned bypalo_altoreceipt
Recorded changes28 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productPalo Alto Networks GlobalProtect App; Palo Alto Networks GlobalProtect UWP Appreceipt
Fixed in6.3.3; 6.2.6; 10.2.14; 10.2.13-h5; 10.1.14-h11receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$5,010over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$5,010 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00164 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A reliance on untrusted input for a security decision in the GlobalProtect app on Windows devices potentially enables a locally authenticated non-administrative Windows user to escalate their privileges to NT AUTHORITY\SYSTEM. GlobalProtect App on macOS, Linux, iOS, Android, Chrome OS and GlobalProtect UWP App are not affected. receipt

NVD's analysis a second authority

weakness
CWE-807
also scored by
psirt@paloaltonetworks.com 7.1 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Amber

check it yourself security.paloaltonetworks.com receipt

Movement the material steps

13 Mar 20250.00043
17 Mar 20250.00016 · scoring model v2025.03.14
15 Jun 20260.0015 · scoring model v2026.06.15
5 Oct 20260.00164
Show all 25 observations
13 Mar 20250.00043
17 Mar 20250.00016
18 Mar 20250.00017
29 Mar 20250.00018
30 Mar 20250.00017
13 Apr 20250.0002
19 May 20250.00023
12 Jul 20250.00032
8 Aug 20250.00023
9 Aug 20250.00026
20 Aug 20250.00023
6 Oct 20250.00025
15 Nov 20250.00027
18 Nov 20250.00037
21 Nov 20250.00027
26 Nov 20250.00029
6 Dec 20250.00032
6 Jan 20260.00034
15 Mar 20260.00098
20 Apr 20260.00063
24 Apr 20260.00054
15 Jun 20260.0015
16 Jul 20260.00154
8 Aug 20260.00161
5 Oct 20260.00164

25 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00164Published2025-03-12Public PoC2025-03-14Index as of2026-10-05

The record had been public for 1 year, 6 months when this index was last written.

Published 2025-03-12 receipt · Public PoC 2025-03-14 receipt · Index as of 2026-10-05 derived

The pattern, elsewhere

This record is one instance of CWE-807, reliance on untrusted inputs in a security decision. The index holds 130 prior instances of this class, 3 KEV-listed. The nearest of its KEV-listed records are drawn beside this. cwe-consequences@4.20

CVE-2026-21509 · Microsoft 365 Apps for Enterpriseonly 1 attribute comparableKEV listed · 2026receipt
CVE-2026-21514 · Microsoft 365 Apps for Enterpriseonly 1 attribute comparableKEV listed · 2026receipt
CVE-2026-34486 · Apache Tomcatonly 1 attribute comparableKEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

130 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

palo alto networks globalprotect app

Of the 2 records in this family, this is the only one holding a stated fix version: 6.3.3; 6.2.6; 10.2.14; 10.2.13-h5; 10.1.14-h11; All.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-0117.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.