CVE-2026-89049: AWS Systems Manager Agent · Server-side request forgery in the Session Manager port forwarding functionality
Source AWS Security Bulletins
Not known to be exploited · fixed in 3.3.4851.0 : patch affected systems soon.
Data as of 26 Oct 2026, 07:57 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.4851.0
Exploitation evidence
Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.
What to do
AI-suggested
A fix is available in AWS Systems Manager Agent version 3.3.4851.0. It is recommended to upgrade to this version to remediate the vulnerability. Until the upgrade is applied, restrict the use of the AWS-StartPortForwardingSessionToRemoteHost document by scoping IAM permissions to limit who can initiate port forwarding sessions.
Description
CVE-2026-89049 is a server-side request forgery (SSRF) vulnerability in the AWS Systems Manager Agent's Session Manager port forwarding feature. An authenticated user with port-forwarding permission can bypass the remote destination denylist due to improper validation of equivalent address representations. This allows the user to reach link-local endpoints and potentially obtain the managed instance's temporary IAM role credentials, enabling actions with those permissions from outside the instance. The vulnerability affects all versions prior to 3.3.4851.0. AWS has released version 3.3.4851.0 to fix this issue. Until upgrading, it is recommended to restrict the use of the AWS-StartPortForwardingSessionToRemoteHost document by scoping IAM permissions.