← console
voxell vciy

CVE-2025-4234: Cortex XDR Microsoft 365 Defender Pack: Cleartext Exposure of Credentials

ROUTINE

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

  1. Upgrade to the fixed version for your release line, or later: 11.0.2-133; 4.6.5 CVE record
  2. 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
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

A problem with the Palo Alto Networks Cortex XDR Microsoft 365 Defender Pack can result in exposure of user credentials in application logs. Normally, these application logs are only viewable by local users and are included when generating logs for troubleshooting purposes. This means that these credentials are exposed to recipients of the application logs.

weakness
CWE-532: Insertion of Sensitive Information into Log File
affected
Palo Alto Networks Cortex XDR Microsoft 365 Defender Pack
versions
No affected-version range in held sources.
fixed in
11.0.2-133; 4.6.5
severity
2.4 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/AU:N/R:U/V:D/RE:M/U:Amber
assigned by
palo_alto
published
2025-09-12

check us security.paloaltonetworks.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

dateEPSSevent
13 Sep 20250.00014
18 Sep 20250.00016
14 Oct 20250.00018
19 Nov 20250.00021
15 Jun 20260.00126scoring model v2026.06.15
9 Jul 20260.00127
13 Aug 20260.00136
2 Oct 20260.00139
12 Oct 20260.00138

17 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.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-10-12 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 11.0.2-133; 4.6.5. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

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-2025-4234', '2026-10-29T23:59:59.999999Z', now());