Skip to main content
VulnerabilityPublished Updated

CVE-2025-11462: AWS Client VPN · Link Following

Affects AWS Client VPNSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 5.2.1 as a priority.

Data as of 16 Nov 2026, 20:24 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.2.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade AWS Client VPN to 5.2.1.

Affected software

ProductAffectedFixed in
AWSClient VPNAffected
  • >=1.3.2 <5.2.1
Fixed in
  • 5.2.1

AI-suggested

AWS has released an official fix in AWS VPN Client for macOS version 5.2.1. Users should upgrade to version 5.2.1 or later to remediate this vulnerability. No other mitigation is indicated by the vendor advisory.

Description

CVE-2025-11462 is a critical vulnerability in AWS VPN Client for macOS versions 1.3.2 through 5.2.0. It involves improper link resolution before file access during log rotation, allowing a local non-administrator user to create a symbolic link from a client log file to a privileged location. This can lead to code execution with root privileges if crafted API calls inject arbitrary code into the log file. AWS recommends upgrading to version 5.2.1 or later to mitigate this issue.

References

Community reviews

Loading reviews…