Skip to main content
CISA Known Exploited Vulnerabilities

Versa Concerto Improper Authentication Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2026-01-22
Remediation due
2026-02-12

Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes
https://security-portal.versa-networks.com/emailbulletins/6830f94328defa375486ff2e ; https://nvd.nist.gov/vuln/detail/CVE-2025-34026

Description

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2025-34026 to the KEV catalog 246 days after its CVE record was published. The median for entries added in 2026 so far is 12.5 days.
  • It is one of 2 Versa entries in the CISA KEV catalog, and the only one added in 2026.
  • Its current EPSS score (80.5%) is higher than that of 63% of CISA KEV entries.

Severity

CVSS 4.0 · CNA · CVSS-B9.2 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableyes
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
Asset not publicly exposed
14 days
KEV due date
2026-02-12
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact partial, 2026-01-23).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Versa
Concerto
12.1.2 to 12.2.0

References

1 links

Record Details

Published
2025-05-21
Last updated
2026-01-23
Assigner (CNA)
VulnCheck
Credited to
ProjectDiscovery; Harsh Jaiswal; Rahul Maini; Parth Malhotra

More from Versa

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.