Stored cross-site scripting in the HTML report generator of aidlc-traceability in AWS AI-DLC Workflows
Affects aidlc-traceability 0.1.0 and later, before commit 96cf0ea, when an actor can modify a project's AI-DLC artifact files. CVSS rates it Medium. Fixed in commit 96cf0ea.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 96cf0ea
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected aidlc-traceability versions: 0.1.0 and later, before commit 96cf0ea. An actor can modify a project's AI-DLC artifact files. A user opens the generated HTML traceability report in a browser.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 96cf0ea
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
The aidlc-traceability command-line tool in AWS AI-DLC Workflows creates HTML traceability reports from project artifacts. A person who can edit a project's artifact files could embed malicious script in titles or descriptions, which would run in the browser of anyone who opens the generated report.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
Affected aidlc-traceability versions: 0.1.0 and later, before commit 96cf0ea. An actor can modify a project's AI-DLC artifact files. A user opens the generated HTML traceability report in a browser.Upgrade to a fixed version: 96cf0ea.
Workaround: Do not open HTML reports generated by an unpatched copy of the tool from untrusted projects.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- AWS aidlc-traceability
Version range not reported
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120497
What does this mean?
The HTML traceability report generated by the tool can include injected script from project artifact files. When a user opens the report in a browser, that script runs and can change the displayed coverage and gap-analysis results and read report contents, including local file paths.Source: aws.amazon.com, github.com
Am I affected, and how do I check?
Versions 0.1.0 and later, before commit 96cf0ea, are affected. The issue requires an actor who can modify a project's AI-DLC artifact files and a user who opens the generated HTML report in a browser. To check, compare the installed copy against commit 96cf0ea.Source: aws.amazon.com, github.com
What should I do about it?
Update aidlc-traceability to commit 96cf0ea or later, which addresses the issue. Until then, do not open HTML reports generated by an unpatched copy of the tool from untrusted projects.Source: aws.amazon.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data