GlobalProtect App: Passwords may be logged in clear text while collecting troubleshooting logs
Under certain circumstances a user's password may be logged in cleartext in the PanGPS.log diagnostic file when logs are collected for troubleshooting on GlobalProtect app (also known as GlobalProtect Agent) for MacOS and Windows. For this issue to occur all of these conditions must be true: (1) 'Save User Credential' option should be set to 'Yes' in the GlobalProtect Portal's Agent configuration, (2) the GlobalProtect user manually selects a gateway, (3) and the logging level is set to 'Dump' while collecting troubleshooting logs. This issue does not affect GlobalProtect app on other platforms (for example iOS/Android/Linux). This issue affects GlobalProtect app 5.0 versions earlier than 5.0.9, GlobalProtect app 5.1 versions earlier than 5.1.2 on Windows or MacOS. Since becoming aware of the issue, Palo Alto Networks has safely deleted all the known GlobalProtectLogs zip files sent by customers with the credentials. We now filter and remove these credentials from all files sent to Customer Support. The GlobalProtectLogs zip files uploaded to Palo Alto Networks systems were only accessible by authorized personnel with valid Palo Alto Networks credentials. We do not have any evidence of malicious access or use of these credentials.
- Published
- May 13, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 22th percentile
- CWE
- CWE-534
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 5.5
- CNA · palo_alto
- 6.8
- 1.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| paloaltonetworks | globalprotect | cpe:2.3:a:paloaltonetworks:globalprotect |
Using globalprotect? Add it to your stack and be the first to know about CVEs like this one. (VPN gateway)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- paloaltonetworks globalprotect5.0.0 and later · before 5.0.9
- paloaltonetworks globalprotect5.1.0 and later · before 5.1.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (palo_alto). Independent of NVD's CPE analysis and usually ahead of it.
Palo Alto Networks GlobalProtect App
- 5.0 and later · before 5.0.9affected
- 5.1 and later · before 5.1.2affected
- 5.0.9 and later · before 5.0*not affected
- 5.1.2 and later · before 5.1*not affected
Same product
paloaltonetworks: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-4232GlobalProtect: Authenticated Code Injection Through Wildcard on macOS34Monitor
- CVE-2021-3057GlobalProtect App: Buffer Overflow Vulnerability When Connecting to Portal or Gateway32Monitor
- CVE-2023-0009GlobalProtect App: Local Privilege Escalation (PE) Vulnerability31Monitor
- CVE-2022-0017GlobalProtect App: Improper Link Resolution Vulnerability Leads to Local Privilege Escalation31Monitor
- CVE-2022-0016GlobalProtect App: Privilege Escalation Vulnerability When Using Connect Before Logon31Monitor
- CVE-2020-1989Global Protect Agent: Incorrect privilege assignment allows local privilege escalation31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Navin VasanPalo Alto Networks during internal security review.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-534 · DEPRECATED: Information Exposure Through Debug Log FilesCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.