CVE-2026-73431: CIRCL Vulnerability-Lookup Stateless Token Replay Account Takeover
HERMES THREAT SCORE & OPERATIONAL EXPLOITABILITY
Target:CIRCL Vulnerability-Lookup (vulnerability-lookup <= 5.5.1) Both CVSS v3.1 (8.8 High) and Hermes Threat Score (82 High) indicate severe exposure. Notably uncovered during automated AI-assisted red-team audits conducted jointly by ENISA and CERT-EU, this flaw illustrates how lack of single-use token invalidation converts transient network eavesdropping into persistent account takeover.
CVE-2026-73431: CIRCL Vulnerability-Lookup Stateless Token Replay Account TakeoverVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
π Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Root Cause: Stateless Tokens & Missing Purpose Binding
Section titled β1. Technical Root Cause: Stateless Tokens & Missing Purpose BindingβIn vulnerability-lookup <= 5.5.1, user registration and password recovery workflows generated stateless signed tokens (using cryptographic timestamp signers):
sequenceDiagram autonumber actor User as Legitimate Analyst actor Attacker as Eavesdropping Adversary participant App as Vulnerability-Lookup Server participant DB as Backend Database
User->>App: Requests password reset (/reset_password) App-->>User: Dispatches email with signed token T Attacker->>User: Intercepts token T via proxy/eavesdropping User->>App: Submits token T with NewPassword_User App->>DB: Updates password (Token T NOT marked as consumed) Note over App,DB: Token T remains valid for 24-72h! Attacker->>App: Replays token T with AttackerPassword App->>DB: Overrides password again - Account successfully hijacked!The flaw results from two core architectural oversights:
- No Single-Use Invalidation: The server verified the cryptographic signature and timestamp of the token against
TOKEN_VALIDITY_PERIOD, but maintained zero persistent state tracking used tokens. Once generated, a token could be submitted arbitrarily many times until its absolute expiration. - Missing Purpose Binding: Tokens lacked explicit intent scoping (
action="activation"vsaction="reset"), allowing token type confusion across different endpoints.
2. Commit Resolution Analysis (bef837242657)
Section titled β2. Commit Resolution Analysis (bef837242657)βCIRCL remediated the vulnerability in commit bef837242657acf680832be56b94428df130ed67 by introducing:
- Random Cryptographic Nonces: A high-entropy random nonce is generated per token request.
- SHA-256 Nonce Hashing: The SHA-256 digest of the active nonce is recorded in the userβs database document.
- Atomic Single-Use Invalidation: When a password change or activation completes, the stored nonce is immediately rotated or cleared, rendering the token instantly invalid.
- Explicit Action Scoping: Tokens must explicitly declare and match the targeted action.
3. Forensic Analysis & Detection Rules
Section titled β3. Forensic Analysis & Detection Rulesβ3.1 Web Server Log Detection (Nginx / Apache)
Section titled β3.1 Web Server Log Detection (Nginx / Apache)βIdentify tokens submitted more than once to authentication endpoints:
grep -E "POST /(activate|reset_password)" /var/log/nginx/access.log \ | grep -o "token=[^ &]*" \ | sort | uniq -c | sort -nr | awk '$1 > 1'(Any token appearing multiple times with successful 200 OK or 302 Found responses from distinct client IP addresses indicates an active replay attack).
3.2 Audit Log Tripwires
Section titled β3.2 Audit Log TripwiresβExamine application logs for rapid successive password_reset_success events for identical account handles within short timeframes.
4. Remediation & Hardening
Section titled β4. Remediation & Hardeningβ- Upgrade Immediately:
Upgrade your
vulnerability-lookupdeployment to version 6.0.0 or later. - Temporary Mitigation (Pre-Patch):
Shorten
TOKEN_VALIDITY_PERIODin your application configuration to a minimal window:TOKEN_VALIDITY_PERIOD = 300 # 5 minutes instead of 86400s - Session Invalidation: Upon applying the patch, revoke all active sessions and force password resets across analyst accounts if proxy logs show token reuse.
5. References
Section titled β5. Referencesβ- Upstream Advisory & Commit: CIRCL
bef837242657acf680832be56b94428df130ed67 - Fixed Version:
vulnerability-lookupRelease 6.0.0 - Auditing Bodies: European Union Agency for Cybersecurity (ENISA) & CERT-EU
- Related Hermes Intelligence: