Loading story…
Veeam disclosed CVE-2024-29855, an authentication bypass vulnerability in Veeam Recovery Orchestrator affecting version 7.0.0.337. The flaw stems from a hardcoded JWT signing secret stored in appsettings.json, allowing forged tokens to be accepted by the application and potentially granting access to the VRO web interface with administrative privileges. Veeam addressed the issue in security guidance published through KB4585.
Independent research showed exploitation is more constrained than a straightforward arbitrary-token forgery because a forged JWT must also correspond to a valid username and role already tracked in the product's in-memory AuthorizationTokenStore and tied to an active UI session. The researcher demonstrated a proof of concept that sprays candidate JWTs across a time window until one aligns with an active session, after which authenticated API access is returned, underscoring the risk to exposed or insufficiently segmented VRO deployments.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Sina Kheirkhah of SummoningTeam published a technical analysis showing the flaw stemmed from a hardcoded JWT signing secret in appsettings.json and explaining how token validation also depended on entries in the in-memory AuthorizationTokenStore. The write-up included a proof of concept that sprayed forged JWTs across a time window until one matched an active session and returned authenticated API access.
Veeam published knowledge base article KB4585 for CVE-2024-29855, describing an authentication bypass vulnerability in Veeam Recovery Orchestrator version 7.0.0.337 and assigning it a CVSS score of 9.0. The advisory said exploitation could allow administrative access to the VRO web UI but required knowledge of a valid username and role tied to an active UI session token.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Siemens disclosed **CVE-2026-56451**, a critical authentication-bypass vulnerability in **Opcenter X** caused by improper validation of the algorithm specified in a JSON Web Token (**JWT**) header. The flaw affects **all versions earlier than `V2604`** and allows an **unauthenticated remote attacker** to forge arbitrary JWTs, bypass authentication, impersonate any user including administrators, and potentially obtain full unauthorized access to the application. The issue is classified as **CWE-347** and was assigned a **CVSS v3.1 vector** of `AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, with reporting indicating a **maximum severity score of 10.0** under both CVSS 3.1 and 4.0. Siemens identified **`V2604`** as the remediation release through its ProductCERT advisory, and no active exploitation was reported at disclosure, although the attack class is considered highly exploitable because JWT algorithm confusion techniques are well known and broadly tooled.
Jul 16, 2026
Attackers are actively exploiting **CVE-2026-5430**, a CVSS 10 authentication-bypass vulnerability affecting WSO2 API Manager, API Control Plane, Traffic Manager, and Universal Gateway. The flaw results from improper JWT signature verification: vulnerable services accept tokens signed with unsupported algorithms, allowing attackers to forge JWTs with administrator privileges and bypass authentication. WatchTowr recorded exploitation attempts against its honeypots using forged administrative tokens. Successful compromise can enable full administrative account takeover and expose API backend endpoints, registered application credentials, consumer keys, and other secrets. Attackers may also be able to intercept data in transit and access internal services reachable through affected API deployments. WSO2 released fixes in April 2026 through community pull requests and subscription update levels; organizations should apply the relevant updates immediately and investigate WSO2 environments for unauthorized administrator tokens or account activity.
Sep 16, 2026
Public advisories disclosed multiple critical vulnerabilities in **CIRCUTOR PowerStudio SCADA WAVE 24.11.6.0**, including a JWT forgery flaw that enables authentication bypass across .NET Core microservices. The issue stems from fail-open JWT validation, allowing attackers to submit forged `alg=none` tokens with arbitrary role claims and gain authenticated access without valid credentials. Researchers said the weakness affects every microservice that trusts the shared identity model, creating broad exposure across the platform. The same research also detailed a **pre-authentication remote code execution chain** that can lead to command execution as `NT AUTHORITY\SYSTEM`. The chain combines the JWT bypass with a path-traversal write to a malicious events configuration and an engine restart to trigger attacker-controlled commands. The advisory said the RCE path requires reachability to **PSSAdministrator** on port `8089`; if that service is restricted to loopback with no forwarding path, a fully remote unauthenticated attacker cannot complete exploitation. Proof-of-concept code and full technical analysis were released publicly by the **0day Rubbish Research Team**.
Aug 6, 2026