Security readout for executives and security teams
Plain-English summary
CVE-2026-64633 is a critical Veeam ONE vulnerability that may let a remote attacker take control of an agent host without credentials or user action. A successful attack could expose, alter, or disrupt data and systems. The supplied version information is incomplete, so organizations should urgently confirm exposure using Veeam’s advisory.
Executive priority
Treat this as an immediate validation and remediation priority. Assign ownership now, identify all Veeam ONE deployments, confirm scope with Veeam, and reduce network exposure while remediation proceeds. Escalation is justified by the maximum CVSS score and unauthenticated remote-code-execution impact, although active exploitation is not established.
Technical view
The issue is classified as CWE-94 code injection and remote unauthenticated code execution. Its CVSS 4.0 score is 10.0, with network access, low complexity, no privileges, and no user interaction required. The vector indicates high confidentiality, integrity, and availability impact to both the vulnerable system and subsequent systems.
Likely exposure
Potential exposure exists where affected Veeam ONE agent components are installed and network-reachable by an attacker. The bundle identifies Veeam ONE but reports version "0" and a default status of unaffected, which is insufficient to determine the actual affected release range. Confirm every deployment against Veeam KB4892.
Exploitation context
The supplied record marks this CVE as absent from KEV, and no cited evidence confirms active exploitation. Nevertheless, unauthenticated network access, low attack complexity, and complete impact metrics make the vulnerability highly attractive. The available sources do not provide an exploit pathway, indicators of compromise, or observed campaign details.
Researcher notes
The public bundle provides minimal technical detail beyond remote unauthenticated code execution, CWE-94, and the CVSS vector. Its affected entry is ambiguous: version "0" is listed while default status is unaffected. Precise vulnerable components, releases, attack surface, fixed versions, and detection artifacts cannot be established from the supplied evidence alone.
Mitigation direction
- Review Veeam KB4892 immediately for authoritative affected versions, updates, and mitigations.
- Apply the vendor-specified update or mitigation after confirming each deployment's release and component status.
- Restrict agent connectivity to trusted management networks and approved administrative systems.
- Reduce external network exposure until affected-status and remediation are verified.
- Follow vendor guidance rather than relying solely on the incomplete version data in the CVE bundle.
Validation and detection
- Inventory all Veeam ONE servers, agents, components, and installed versions.
- Compare each asset against the affected-version guidance in Veeam KB4892.
- Verify vulnerable services are inaccessible from untrusted networks and unnecessary network paths.
- Confirm the vendor-prescribed update or mitigation is present and operational.
- Review host telemetry for unexpected processes or activity, noting that no specific indicators were supplied.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64633 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——hackeroneVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.veeam.com/kb4892CVE reference, hackerone
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.