# CVE-2026-120497: Stored cross-site scripting in the HTML report generator of aidlc-traceability in AWS AI-DLC Workflows


- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-gjmq-52p3-7fh2

## What is CVE-2026-120497?

CVE-2026-120497 is a medium-severity vulnerability in AWS aidlc-traceability, published on 2 Nov 2026. 

### Official description

Stored cross-site scripting (XSS) in the HTML report generator in the aidlc-traceability CLI in AWS AI-DLC Workflows before 2026-07-03 might allow an actor who can modify a project's AI-DLC artifact files to execute arbitrary script in the browser of a user who opens a generated HTML traceability report via crafted artifact titles or descriptions.

To remediate this issue, users should remove any local copy of the aidlc-traceability CLI obtained before 2026-07-03, or update it to commit 96cf0ea or later. The CLI was removed from the repository on 2026-07-16.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-120497?


## How do I fix CVE-2026-120497?

No fix has been published for CVE-2026-120497 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120497 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120497 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120497 and fix it if it is affected.

What it is: CVE-2026-120497 is a medium-severity vulnerability in AWS aidlc-traceability, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120497 exists.

Affected product: AWS aidlc-traceability. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120497/ (Markdown: https://insights.sbomify.com/CVE-2026-120497/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120497
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120497
- OSV: https://osv.dev/vulnerability/CVE-2026-120497

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120497/
Summaries are generated and may contain mistakes; the official description above is the record.
