LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20625: A parsing issue in the handling of directory paths was addressed with improved path validation.

A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3, visionOS 26.3. An app may be able to access sensitive user data.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-20625 is an Apple path-handling flaw that could let an app access sensitive user data. Apple fixed it with improved path validation in listed macOS and visionOS releases. Business urgency is moderate: it affects confidentiality, but the CVSS vector indicates local access and user interaction are required.

Executive priority

Treat this as a routine but important Apple security update. Prioritize managed devices handling sensitive data and environments where users can install or run untrusted apps. There is no sourced evidence of active exploitation, but confidentiality impact is high if abused.

Technical view

The issue is described as improper handling of directory paths, mapped to CWE-22. Apple states an app may access sensitive user data. CVSS 3.1 is 5.5 with local attack vector, low complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality impact only.

Likely exposure

Exposure is likely on Apple endpoints or visionOS devices running versions earlier than macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3, or visionOS 26.3. The source bundle does not identify specific vulnerable subcomponents beyond Apple’s platform advisories.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked in KEV. The CVSS vector suggests exploitation requires a local context and user interaction, consistent with a malicious or untrusted app scenario rather than unauthenticated remote compromise.

Researcher notes

Available public detail is limited. The vulnerability is a directory path parsing issue addressed by improved path validation. Avoid assuming a specific reachable service or sandbox boundary without Apple’s additional detail. Validation should focus on version exposure and advisory coverage, not exploit reproduction.

Mitigation direction

  • Update macOS Sequoia systems to 15.7.4 or later where applicable.
  • Update macOS Sonoma systems to 14.8.4 or later where applicable.
  • Update macOS Tahoe systems to 26.3 or later where applicable.
  • Update visionOS devices to 26.3 or later where applicable.
  • Review Apple advisories for any deployment-specific guidance.

Validation and detection

  • Inventory macOS and visionOS versions across managed assets.
  • Confirm fixed versions are installed on in-scope devices.
  • Check MDM or endpoint management reports for update compliance.
  • Prioritize devices used with sensitive data or untrusted applications.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-20625 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-20625Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ApplemacOS0, 0, 0Listed
ApplevisionOS0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.