dbcve.org
Amplify Codegen UiApplication · Amazon

CVE-2026-18245

HIGH · 8.8 CVSS v3.1 Published 2026-07-30
Fix available
A fix is available. Upgrade to 2.20.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper control of code generation in Amazon @aws-amplify/codegen-ui-react before 2.20.6 might allow a remote authenticated user to execute arbitrary code in end-user browsers, developer machines, CI/CD environments, and server-side rendering contexts via crafted Studio component or theme schema values due to insufficient coverage and effectiveness of the input validation introduced for CVE-2025-4318. To remediate this issue, users should upgrade to version 2.20.6

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper control of code generation in Amazon @aws-amplify/codegen-ui-react before 2.20.6 allows authenticated users to inject arbitrary code through crafted Studio component or theme schema values. This is a bypass of CVE-2025-4318, where input validation coverage and effectiveness were insufficient, enabling code execution in end-user browsers, developer machines, CI/CD pipelines, and SSR contexts.

MitigationUpgrade @aws-amplify/codegen-ui-react to version 2.20.6 or later to obtain the improved input validation that addresses this code injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Amplify Codegen UiApplication
Affected:< 2.20.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed @aws-amplify/codegen-ui-react version
    Run 'npm list @aws-amplify/codegen-ui-react' or inspect the version in package.json under dependencies or devDependencies
    Affected if The installed version is lower than 2.20.6
  2. Verify codegen command usage
    Check if your project runs 'amplify codegen' or uses the codegen API to generate UI code from Studio component or theme schemas
    Affected if Your project uses codegen to process Studio component or theme schema files (typically .json schema files from Amplify Studio)
  3. Identify schema input sources
    Review your project for Studio component schema files (usually in amplify/backend/api/*/schema.graphql or custom component schema .json files) and theme schema .json files processed by codegen
    Affected if You have custom or imported Studio component schemas or theme schemas that are fed into the codegen process

You are affected if @aws-amplify/codegen-ui-react version is below 2.20.6 AND your project processes Studio component or theme schemas through codegen, as crafted malicious schema values could trigger arbitrary code execution during code generation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.20.6 or later
Fixed in 2.20.6
Interim mitigation

Upgrade @aws-amplify/codegen-ui-react to version 2.20.6 or later to obtain the improved input validation that addresses this code injection vulnerability.

Recommended fix High confidence

2.20.6

  1. Update the @aws-amplify/codegen-ui-react package to version 2.20.6 or later
  2. Run npm install @aws-amplify/[email protected] or yarn add @aws-amplify/[email protected] to install the fixed version
  3. Rebuild and redeploy any applications using this package to ensure the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amplify Codegen Ui Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-18245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-18245 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data