Skip to main content
Mallory
HighVulnerability

CVE-2026-58075: Unauthenticated Arbitrary File Read in Veeam ONE

Published Aug 4, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-58075CWE-287 · Improper Authentication

CVE-2026-58075 is an improper authentication vulnerability in Veeam ONE that allows an unauthenticated network attacker to read arbitrary files from the host. The disclosed affected builds include Veeam ONE 13.0.2.6723 and earlier version 13 builds. Disclosed information can potentially be leveraged for local privilege escalation. The vulnerability has a CVSS v4.0 score of 8.7. The specific vulnerable function and underlying implementation details are not available.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises host file confidentiality and can expose sensitive configuration data, credentials, logs, and other information. The disclosed information may support subsequent local privilege escalation. The direct file-read vulnerability is rated as having high confidentiality impact, with no direct integrity or availability impact.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific temporary workaround is documented. Pending patch deployment, restrict network access to Veeam ONE servers and agents to trusted administrative systems and review unnecessary exposure. These restrictions reduce exposure but do not replace the security update.

Remediation

Patch, then assume compromise.

Install Veeam ONE 13.1.0.7034 or a later supported fixed release. For deployments remaining on the 13.0 branch, install build 13.0.2.7159, which also fixes CVE-2026-58075. Follow Veeam's applicable upgrade instructions and verify the installed build after updating.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-58075 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-58075 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58075?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-58075.
Is there a patch for CVE-2026-58075?
Install Veeam ONE 13.1.0.7034 or a later supported fixed release. For deployments remaining on the 13.0 branch, install build 13.0.2.7159, which also fixes CVE-2026-58075.
How severe is CVE-2026-58075?
CVE-2026-58075 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.42% (37th percentile) as of Nov 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.