CERTFR-2026-AVI-0968

Vulnerability from certfr_avis - Published: 2026-08-05 - Updated: 2026-08-05

De multiples vulnérabilités ont été découvertes dans les produits Veeam. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance.

Solutions

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

Impacted products
Vendor Product Description
Veeam Veeam ONE Veeam ONE versions antérieures à 13.1.0.7034
Veeam Veeam Service Provider Console Service Provider Console versions antérieures à 9.3.0.35057
References
Bulletin de sécurité Veeam kb4892 2026-07-29 vendor-advisory
Bulletin de sécurité Veeam kb4893 2026-08-04 vendor-advisory

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Veeam ONE versions ant\u00e9rieures \u00e0 13.1.0.7034",
      "product": {
        "name": "Veeam ONE",
        "vendor": {
          "name": "Veeam",
          "scada": false
        }
      }
    },
    {
      "description": "Service Provider Console versions ant\u00e9rieures \u00e0 9.3.0.35057",
      "product": {
        "name": "Veeam Service Provider Console",
        "vendor": {
          "name": "Veeam",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": "",
  "content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
  "cves": [
    {
      "name": "CVE-2026-64633",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64633"
    },
    {
      "name": "CVE-2026-58067",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58067"
    },
    {
      "name": "CVE-2026-58072",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58072"
    },
    {
      "name": "CVE-2026-58075",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58075"
    },
    {
      "name": "CVE-2026-58073",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58073"
    },
    {
      "name": "CVE-2026-58074",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58074"
    },
    {
      "name": "CVE-2026-58071",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-58071"
    },
    {
      "name": "CVE-2026-64630",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64630"
    },
    {
      "name": "CVE-2026-64634",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64634"
    },
    {
      "name": "CVE-2026-64631",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64631"
    }
  ],
  "initial_release_date": "2026-08-05T00:00:00",
  "last_revision_date": "2026-08-05T00:00:00",
  "links": [],
  "reference": "CERTFR-2026-AVI-0968",
  "revisions": [
    {
      "description": "Version initiale",
      "revision_date": "2026-08-05T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Injection SQL (SQLi)"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits Veeam. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une \u00e9l\u00e9vation de privil\u00e8ges et un d\u00e9ni de service \u00e0 distance.",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits Veeam",
  "vendor_advisories": [
    {
      "published_at": "2026-07-29",
      "title": "Bulletin de s\u00e9curit\u00e9 Veeam kb4892",
      "url": "https://www.veeam.com/kb4892"
    },
    {
      "published_at": "2026-08-04",
      "title": "Bulletin de s\u00e9curit\u00e9 Veeam kb4893",
      "url": "https://www.veeam.com/kb4893"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.