Quick answers
- Is CVE-2026-120497 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120497 being exploited in the wild.
- How severe is CVE-2026-120497?
- High severity, with a CVSS score of 5, published 2 November 2026.
- Which products and versions are affected?
- AWS AI-DLC Workflows aidlc-traceability >=0.1.0 before commit 96cf0ea (2026-07-03).
- Is there a fix for CVE-2026-120497?
- Yes: fixed in commit 96cf0ea (2026-07-03); tool subsequently removed from awslabs/aidlc-workflows on 2026-07-16. Until then: Do not open HTML reports generated by an unpatched copy of the tool from untrusted projects. Use Markdown report output instead of HTML, or regenerate reports only from artifact files you control, until you update or remove the local copy. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120497 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120497?
- Check whether you run Amazon AWS or AWS AI-DLC Workflows aidlc-traceability at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: commit 96cf0ea (2026-07-03); tool subsequently removed from awslabs/aidlc-workflows on 2026-07-16
Do not open HTML reports generated by an unpatched copy of the tool from untrusted projects. Use Markdown report output instead of HTML, or regenerate reports only from artifact files you control, until you update or remove the local copy.
Technical details
Stored XSS in the HTML report generator where unsanitized artifact titles and descriptions are embedded into HTML without proper escaping, allowing script injection via crafted artifact metadata. The vulnerability requires an attacker with write access to project artifact files; users viewing the generated HTML report from untrusted projects are at risk. The fix (commit 96cf0ea, 2026-07-03) sanitizes embedded JSON and hardens file-read boundaries.
Affected products
- AWS AI-DLC Workflows aidlc-traceability >=0.1.0 before commit 96cf0ea (2026-07-03)
Timeline
- 2026-11-02: disclosed
- 2026-07-03: patched: commit 96cf0ea