npm package report

Is @aws-amplify/cli safe?

1 known vulnerability, worst severity CRITICAL.

cvss
9.8

how bad it is if exploited, out of 10

epss
1.7%

chance of exploitation in the next 30 days

xyz score
5.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-846g-p7hm-f54r, the advisory selected below

// advisories

GHSA-846g-p7hm-f54r

CRITICALCVE-2024-28056

Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM roles associated with Amplify projects. When the Authentication component is removed from an Amplify project, a Condition property is removed but "Effect":"Allow" remains present, and consequently sts:AssumeRoleWithWebIdentity would be available to threat actors with no conditions. Thus, if Amplify CLI had be

Affected
< 12.10.1
Fixed in
12.10.1
Weakness
CWE-269
Published
2024-04-15
Source
github

GHSANVDMITREreferencereferencereferencereferencereference

// dependencies

3 direct, 1 carrying known advisories, worst HIGH

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 03:27 UTC. The most recent advisory here was published 2024-04-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @aws-amplify/cli safe? npm package security report | CyberXYZ