CVE-2025-2598: AWS Cloud Development Kit Command Line Interface · Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affects AWS Cloud Development Kit Command Line InterfaceSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium · fixed in 2.178.2 : update AWS Cloud Development Kit Command Line Interface when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.178.2
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWS Cloud Development Kit Command Line Interface | Affected
| Fixed in– |
AI-suggested
European organizations should immediately upgrade AWS CDK CLI installations to version 2.178.2 or later to remediate this vulnerability. They should audit all environments where AWS CDK CLI is used, including CI/CD pipelines, developer workstations, and build servers, to ensure no outdated versions remain in use. Any forked or customized versions of the AWS CDK CLI must be reviewed and patched to incorporate the fix. Organizations should also review logging and monitoring configurations to ensure console outputs containing sensitive credentials are not stored or accessible to unauthorized personnel. Implementing strict access controls on developer and build environments can reduce the risk of unauthorized local access. Additionally, rotating AWS credentials that may have been exposed prior to patching is recommended. Finally, educating developers and DevOps teams about secure handling of credentials and the risks of exposing them in logs or console outputs will help prevent similar issues.
Description
When the AWS Cloud Development Kit (AWS CDK) Command Line Interface (AWS CDK CLI) is used with a credential plugin which returns an expiration property with the retrieved AWS credentials, the credentials are printed to the console output. To mitigate this issue, users should upgrade to version 2.178.2 or later and ensure any forked or derivative code is patched to incorporate the new fixes.