Quick answers
- Is CVE-2026-13140 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13140 being exploited in the wild.
- How severe is CVE-2026-13140?
- Informational severity, with a CVSS score of 2, published 24 June 2026.
- Which products and versions are affected?
- Thinkst Applied Research Canarytokens Docker tag sha-4116b92cb before sha-f5aa5c4e, Git commit 4116b92cb before f5aa5c4e.
- Is there a fix for CVE-2026-13140?
- A patch was published on 2026-06-24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13140 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-13140?
- Check whether you run Thinkst Applied Research Canarytokens 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.
Technical details
A stored Cross-Site Scripting (XSS) vulnerability exists in the 'public_location' field of the AWS API key store in Thinkst Canarytokens. The root cause is improper neutralization of input during web page generation, where the affected field is rendered in the UI without sufficient sanitization. To exploit this, an attacker requires knowledge of a random, unguessable identifier and must convince a victim to click a rendered link. Successful exploitation allows the execution of JavaScript in the victim's browser within the canarytokens.org domain, though impact is limited to extracting details about the targeted AWS API Key Canarytoken as the site does not utilize user sessions. The issue is patched in Docker tag sha-f5aa5c4e and Git commit f5aa5c4e.
Affected products
- Thinkst Applied Research Canarytokens Docker tag sha-4116b92cb before sha-f5aa5c4e, Git commit 4116b92cb before f5aa5c4e
Timeline
- 2026-06-24: disclosed
- 2026-06-24: advisory
- 2026-06-24: patched