CVE-2024-5921: GlobalProtect App: Insufficient Certificate Validation Leads to Privilege Escalation
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 6.3.2; 6.2.6; 6.2.6-c857; 6.2.1-c31; 6.1.6; 6.1.7 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
An insufficient certification validation issue in the Palo Alto Networks GlobalProtect app enables attackers to connect the GlobalProtect app to arbitrary servers. This can enable a local non-administrative operating system user or an attacker on the same subnet to install malicious root certificates on the endpoint and subsequently install malicious software signed by the malicious root certificates on that endpoint. Please subscribe to our RSS feed https://security.paloaltonetworks.com/rss.xml to be alerted to new updates to this and other advisories.
- weakness
- CWE-295 Improper Certificate Validation
- affected
- Palo Alto Networks GlobalProtect App
- published ranges
- paloaltonetworks globalprotect >= 6.1.0 < 6.1.6; paloaltonetworks globalprotect >= 6.1.0 < 6.1.7; paloaltonetworks globalprotect >= 6.1.0 < 6.2.1; paloaltonetworks globalprotect >= 6.1.0 < 6.2.6; and 1 more on the CVE page
- fixed in
- 6.3.2; 6.2.6; 6.2.6-c857; 6.2.1-c31; 6.1.6; 6.1.7
- severity
- 6 CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/AU:N/R:U/V:D/RE:M/U:Amber
- assigned by
- palo_alto
- published
- 2024-11-27
check us security.paloaltonetworks.com blog.amberwolf.com github.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 27 Nov 2024 | 0.00045 | |
| 17 Mar 2025 | 0.00012 | scoring model v2025.03.14 |
| 27 Mar 2025 | 0.00013 | |
| 28 Mar 2025 | 0.00012 | |
| 18 Apr 2026 | 0.00376 | |
| 15 Jun 2026 | 0.01425 | scoring model v2026.06.15 |
| 22 Jun 2026 | 0.01454 | |
| 3 Sep 2026 | 0.01456 |
26 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-09-03 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 6.3.2; 6.2.6; 6.2.6-c857; 6.2.1-c31; 6.1.6; 6.1.7. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-5921', '2026-10-30T23:59:59.999999Z', now());