CVE-2022-0026: Cortex XDR Agent: Unintended Program Execution Leads to Local Privilege Escalation (PE) Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A local privilege escalation (PE) vulnerability exists in Palo Alto Networks Cortex XDR agent software on Windows that enables an authenticated local user with file creation privilege in the Windows root directory (such as C:\) to execute a program with elevated privileges. This issue impacts all versions of Cortex XDR agent without content update 330 or a later content update version.
- Published
- May 11, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-282
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 6.7
- CNA · palo_alto
- 6.7
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| paloaltonetworks | cortex xdr agent | cpe:2.3:a:paloaltonetworks:cortex_xdr_agent |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- paloaltonetworks cortex xdr agent6.1
- paloaltonetworks cortex xdr agent6.1.4
- paloaltonetworks cortex xdr agent6.1.5
- paloaltonetworks cortex xdr agent6.1.6
- paloaltonetworks cortex xdr agent6.1.7
- paloaltonetworks cortex xdr agent6.1.8
- paloaltonetworks cortex xdr agent6.1.9
- paloaltonetworks cortex xdr agent7.4.1
- paloaltonetworks cortex xdr agent7.4.2
- paloaltonetworks cortex xdr agent7.4.3
- paloaltonetworks cortex xdr agent7.4.4
- paloaltonetworks cortex xdr agent7.5
- paloaltonetworks cortex xdr agent7.5.1
- paloaltonetworks cortex xdr agent7.5.2
- paloaltonetworks cortex xdr agent7.5.3
- paloaltonetworks cortex xdr agent7.6.1
- paloaltonetworks cortex xdr agent7.6.2
- paloaltonetworks cortex xdr agent7.7
- paloaltonetworks cortex xdr agent7.7.1
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 Cortex XDR Agent
- 7.7.* with CU-330, 7.6.* with CU-330, 7.5 CE 7.5.* with CU-330, 7.4.* with CU-330, 6.1.* with CU-330, 7.5.* with CU-330not affected
- 7.7.* without CU-330, 7.6.* without CU-330, 7.5 CE 7.5.* without CU-330, 7.4.* without CU-330, 6.1.* without CU-330, 7.5.* without CU-330affected
Same product
paloaltonetworks: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-0002Cortex XDR Agent: Product Disruption by Local Windows User31Monitor
- CVE-2022-0015Cortex XDR Agent: An Uncontrolled Search Path Element Leads to Local Privilege Escalation (PE) Vulnerability31Monitor
- CVE-2021-3042Cortex XDR Agent: Improper Control of User-Controlled File Leads to Local Privilege Escalation31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-0014Jan 12, 2022 · Cortex XDR Agent: Unintended Program Execution When Using Live Terminal Session29Monitor
- ← EarlierCVE-2022-0025May 11, 2022 · Cortex XDR Agent: An Uncontrolled Search Path Element Leads to Local Privilege Escalation (PE) Vulnerability26Monitor
- Later →CVE-2022-0029Sep 14, 2022 · Cortex XDR Agent: Improper Link Resolution Vulnerability When Generating a Tech Support File22Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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.
- Xavier DANESTDecathlon and Yasser Alhazmi for discovering and reporting this issue.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0347 · May 12, 2022(Palo Alto Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-282 · Improper Ownership ManagementCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change 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.