Cyber Resilience

CVE-2026-10729

Published
03 June 2026
Modified
22 July 2026
CVSS Score v4 1.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:X/V:X/RE:L/U:Green
EPSS Score 0.0020 11th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-10729 is a low-severity Injection (CWE-74) vulnerability. Its CVSS base score is 1.2 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

An HTML injection vulnerability in the notification email for "Slow Redirect" and "Cloned Website" Canarytokens exists in Thinkst Applied Research Canarytokens, enabling Interface Manipulation, Cross-Site Scripting (XSS) in emails clients that render HTML emails. This issue affects Canarytokens: from Docker…

more

tag sha-c42435e before sha-bfda4df, from Git commit c42435e before bfda4df.

CWE(s)
CWE-74

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Why these techniques?

HTML injection vuln directly enables email content injection (T1659) leading to XSS.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-41237Shared CWE-74
CVE-2026-0972Shared CWE-74
CVE-2026-0865Shared CWE-74
CVE-2025-9797Shared CWE-74
CVE-2024-10491Shared CWE-74
CVE-2025-67746Shared CWE-74
CVE-2026-35515Shared CWE-74
CVE-2026-47644Shared CWE-74
CVE-2026-1154Shared CWE-74
CVE-2025-20216Shared CWE-74

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-15 Information Output Filtering
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Directly requires validation and sanitization of untrusted data (token metadata) before it is inserted into notification email bodies, blocking the HTML injection.

SI-15 Information Output Filtering good match
prevent

Mandates filtering of outbound information to remove or encode dangerous HTML/JS constructs, preventing XSS in email clients that render the Canarytoken notifications.

SI-7 Software, Firmware, and Information Integrity partial match
detect

Provides integrity verification of email templates and generated notification content, allowing detection of unauthorized HTML modifications introduced by the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
detects

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
detects

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.

References