Versa Concerto Improper Authentication Vulnerability
Exploited since 2026-01-22. 2 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: not blocked.
The Versa Concerto SD-WAN orchestration platform is vulnerable to an authentication bypass in the Traefik reverse proxy configuration, allowing at attacker to access administrative endpoints. The internal Actuator endpoint can be leveraged… More
The Versa Concerto SD-WAN orchestration platform is vulnerable to an authentication bypass in the Traefik reverse proxy configuration, allowing at attacker to access administrative endpoints. The internal Actuator endpoint can be leveraged for access to heap dumps and trace logs.This issue is known to affect Concerto from 12.1.2 through 12.2.0. Additional versions may be vulnerable.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 4.0Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality; other systems can also be hit (full loss of confidentiality and low impact on integrity).
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityNo built-in defences have to be bypassed; the attack works reliably.Low
- Attack requirementsThe attack works without any special deployment or timing conditions.None
- Privileges requiredNo account or login is needed.None
- User interactionNo one has to click or open anything; the attack works on its own.None
- Confidentiality impact (vulnerable system)An attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impact (vulnerable system)Data cannot be changed by the attacker.None
- Availability impact (vulnerable system)The component keeps working normally.None
- Confidentiality impact (other systems)Other systems that rely on it can have all their data read.High
- Integrity impact (other systems)Other systems that rely on it can have some data changed.Low
- Availability impact (other systems)Other systems keep working normally.None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:NAttackers are exploiting this in the wild.
Attackers can script the attack end to end and hit many targets at once.
A successful attack gives limited control over the affected software or limited access to its data.
Public exploits
1 found- NucleiCVE-2025-34026.yamldetection template, replayed in our lab
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-05-21CVE publishedCVE List
- 2025-06-02Cloudflare ships a ruleVersa Concerto SD-WAN - Auth Bypass - CVE:CVE-2025-34026
- 2025-08-15F5 ships a ruleVersa Concerto Actuator Authentication Bypass
- 2026-01-22Added to CISA KEVConfirmed exploitation in the wild
- 2026-11-02Our test: OWASP Core Rule Set let it throughparanoia level 1, anomaly threshold 5, default CRS settings
- 2026-11-02Our test: OWASP Core Rule Set let it throughparanoia level 2, anomaly threshold 5, default CRS settings
Vendor statements
QuotedCloudflareWAF Managed Rules
First rule 2025-06-02, 12 days after the CVE was published.
Versa Concerto SD-WAN - Auth Bypass - CVE:CVE-2025-34026. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-08-15, 86 days after the CVE was published.
Added: signature 200013124 "Versa Concerto Actuator Authentication Bypass" (Authentication/Authorization Attacks, risk High), systems: Other Web Server. References: CVE-2025-34026.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.