Connected & Protected
24/7 Support
HomeBlogHoles in Veeam Backup suite allow remote code execution, creation of malicious backup config files
Security, Vulnerabilities
#Security, Vulnerabilities
#Veeam Backup vulnerabilities
#remote code execution Veeam
#CVE-2025-59470
#Veeam Backup patch
#backup configuration security
#cybersecurity vulnerabilities
#Veeam Backup & Replication
#data protection best practices
#backup system security threats
#IT security updates
#Veeam Backup user roles
#malicious configuration files

Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files

Veeam says that four vulnerabilities could allow a person with certain oversight roles for its flagship Backup & Replication suite to do serious damage to – but not destroy – a backup database. The company has already issued a patch for the bugs, which, it says, should be applied immediately. The worst of the vulnerabilities, CVE-2025-59470, carries a criticality score of 9 and would allow a threat actor “to do something nefarious,” said Rick Vanover, Veeam’s vice-president of product strategy. But he emphasized that, because of the immutable nature of the backup, data can’t be destroyed. The issue: Veeam discovered that a person with the role of Backup Admin, Backup Operator, or Tape Operator status in unpatched version 13 of the suite (versions 13.0.1.180 and earlier) have more permissions than they should. The patch corrects that. Specifically, the flaws addressed are: CVE-2025-59470 (with a CVSS score of 9) allows a Backup or Tape Operator to perform remote code execution (RCE) as the Postgres user by sending a malicious interval or order parameter; CVE-2025-59469 (with a severity score of 7.2) allows a Backup or Tape Operator to write files as root; CVE-2025-55125 (with a severity score of 7.2) allows a Backup or Tape Operator to perform remote code execution (RCE) as root by creating a malicious backup configuration file; CVE-2025-59468 (with a severity score of 6.7) allows a Backup Administrator to perform remote code execution (RCE) as the Postgres user by sending a malicious password parameter. The patch to version 13.0.1.1071 will be an “easy installation” that won’t be disruptive, Vanover said. As of Tuesday afternoon, Veeam hadn’t received reports of exploitation, he added. “The good news is, if a Veeam server is broken, we can create a new server right away – presumably with this patch installed – import the backups and carry on. The core data is completely unimpacted by this,” Vanover said. “The worst type of thing would be the [backup] environment isn’t working right or the Postgres database is messed up on the Veeam server, so jobs might not behave in a way one might expect.” In these cases, admins using the Veeam One monitoring management suite would get an alert if, for example, a job was unable to connect to the backup server or backup jobs were failing. The four vulnerabilities being patched are less severe than some because an attacker, internal or external, would need valid credentials for the three specific roles, noted Johannes Ullrich, dean of research at the SANS Institute. On the other hand, he added, backup systems like Veeam are targets for attackers, in particular those who inject ransomware, who often attempt to erase backups. “Backup systems should be regularly audited to ensure that access rights, such as those mentioned in this vulnerability, are properly managed and only accessible to users who actually need them,” he said. “Authentication credentials should be reviewed to ensure they comply with the respective standards.” Kellman Meghu, principal security architect at Canadian-based risk management firm DeepCove Cybersecurity, said the worry is how the vulnerabilities could be used by a threat actor to get root privileges to the backup, “which is the worst it can get as far as compromise. From the sounds of the exploit, just being able to update a config file could be the avenue for executing malicious commands at the highest privileges.” Admins who can’t patch quickly, or who have been running unpatched versions for any length of time, should first audit all config files and operations to ensure there have been no changes to the config files or execution of additional unexpected actions. Alerts should be set for every backup process run, so it is closely monitored until the suite can be patched. “Keep in mind,” he added, “if you do see unusual behavior, it is a sign that there is a malicious actor or inside threat operating, and you would need to take a holistic incident response.” This article originally appeared on NetworkWorld.

C
Cybersecurity at the edge: Securing rugged IoT in mission-critical environments | CSO Online
Content Author
Content Specialist

Cybersecurity expert with extensive experience in protecting critical systems and data. Specializes in identifying vulnerabilities and implementing robust security measures in backup solutions.

Expertise: Cybersecurity, Vulnerability Management, IT Security, Data Protection, Backup Solutions
Published: January 8, 2026
6 min read

Quick Answer

Recent vulnerabilities in Veeam Backup Suite could lead to remote code execution and unauthorized file creation. Users must apply the latest patch to mitigate these risks.

TL;DR

Veeam Backup Suite has four vulnerabilities that allow remote code execution under specific user roles. The company has issued a patch, and users are urged to audit their configurations and monitor backup jobs closely.

Key Takeaways

  • 1Four vulnerabilities in Veeam Backup Suite can lead to remote code execution.
  • 2A critical patch is available for immediate installation to secure the software.
  • 3Regular monitoring of backup jobs is essential to prevent exploitation.
Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files

Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files

The vendor has issued a patch to close four holes in its flagship Backup & Replication suite; version 13 users are advised to audit their backup config files and closely monitor backup jobs.

Credit: Shutterstock

Veeam says that four vulnerabilities could allow a person with certain oversight roles for its flagship Backup & Replication suite to do serious damage to – but not destroy –  a backup database.

The company has already issued a patch for the bugs, which, it says, should be applied immediately.

The worst of the vulnerabilities, CVE-2025-59470, carries a criticality score of 9 and would allow a threat actor “to do something nefarious,” said , Veeam’s vice-president of product strategy.

But he emphasized that, because of the immutable nature of the backup, data can’t be destroyed.

The issue: Veeam discovered that a person with the role of Backup Admin, Backup Operator, or Tape Operator status in unpatched version 13 of the suite (versions 13.0.1.180 and earlier) have more permissions than they should. The patch corrects that.

  • CVE-2025-59470 (with a CVSS score of 9) allows a Backup or Tape Operator to perform remote code execution (RCE) as the Postgres user by sending a malicious interval or order parameter;
  • CVE-2025-59469 (with a severity score of 7.2) allows a Backup or Tape Operator to write files as root;
  • CVE-2025-55125 (with a severity score of 7.2) allows a Backup or Tape Operator to perform remote code execution (RCE) as root by creating a malicious backup configuration file;
  • CVE-2025-59468 (with a severity score of 6.7) allows a Backup Administrator to perform remote code execution (RCE) as the Postgres user by sending a malicious password parameter.

The patch to version 13.0.1.1071 will be an “easy installation” that won’t be disruptive, Vanover said. As of Tuesday afternoon, Veeam hadn’t received reports of exploitation, he adde

CrowdStrike
Related Product

CrowdStrike Advanced Defend

by CrowdStrike$15.41/mo

CrowdStrike provides advanced cloud-native platform protection for endpoints, cloud workloads, identities, and data with a single lightweight agent.

Learn More
d.

“The good news is, if a Veeam server is broken, we can create a new server right away – presumably with this patch installed – import the backups and carry on. The core data is completely unimpacted by this,” Vanover said. “The worst type of thing would be the [backup] environment isn’t working right or the Postgres database is messed up on the Veeam server, so jobs might not behave in a way one might expect.”

In these cases, admins using the Veeam One monitoring management suite would get an alert if, for example, a job was unable to connect to the backup server or backup jobs were failing.

The four vulnerabilities being patched are less severe than some because an attacker, internal or external, would need valid credentials for the three specific roles, noted Johannes Ullrich, dean of research at the SANS Institute.

On the other hand, he added, backup systems like Veeam are targets for attackers, in particular those who inject ransomware, who often attempt to erase backups.

“Backup systems should be regularly audited to ensure that access rights, such as those mentioned in this vulnerability, are properly managed and only accessible to users who actually need them,” he said. “Authentication credentials should be reviewed to ensure they comply with the respective standards.”

, principal security architect at Canadian-based risk management firm DeepCove Cybersecurity, said the worry is how the vulnerabilities could be used by a threat actor to get root privileges to the backup, “which is the worst it can get as far as compromise. From the sounds of the exploit, just being able to update a config file could be the avenue for executing malicious commands at the highest privileges.”

Admins who can’t patch quickly, or who have been running unpatched versions for any length of time, should first audit all config files and operations to ensure there have been no changes to the config files or execution of additional unexpected actions. Alerts should be set for every backup process run, so it is closely monitored until the suite can be patched.

“Keep in mind,” he added, “if you do see unusual behavior, it is a sign that there is a malicious actor or inside threat operating, and you would need to take a holistic incident response.”

This article originally appeared on NetworkWorld.

Howard Solomon is a Toronto-based freelance reporter who writes on IT and cybersecurity issues.

Howard is a former editor of IT World Canada and Computing Canada. An IT journalist over 30 years, he has also written for ITBusiness.ca and Computer Dealer News. Before that he was a staff reporter at the Calgary Herald and the Brampton (Ontario) Daily Times.

Patch Tuesday 2025 roundup: The biggest Microsoft vulnerabilities of the year

Dec 30, 2025 7 mins
  • news

    Interpol sweep takes down cybercrooks in 19 countries

    Dec 23, 2025 7 mins
  • news

    HPE OneView vulnerable to remote code execution attack

    Dec 18, 2025 3 mins
  • news

    Microsoft warns MSMQ may fail after update, breaking apps

    Dec 17, 2025 5 mins
  • news

    FortiGate firewall credentials being stolen after vulnerabilities discovered

    Dec 16, 2025 4 mins
  • news

    Meet ConsentFix, a new twist on the ClickFix phishing attack

    Dec 11, 2025 6 mins
  • news

    Fortinet admins urged to update software to close FortiCloud SSO holes

    Dec 10, 2025 4 mins
  • Show me more

    Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files

    Critical RCE flaw allows full takeover of n8n AI workflow platform

    How to eliminate IT blind spots in the modern, AI-driven enterprise

    Inside Visa’s Cyber Defense: CISO Subra Kumaraswamy on blending AI and Human Defense

    CISO Reality: Record Pay, Rising Pressure, and Retention Risk

    The Future of Cybersecurity Leadership: AI, Governance & Education | Kevin Powers, Boston College

    Inside Visa’s Cyber Defense: CISO Subra Kumaraswamy on blending AI and Human Defense

    CSO Executive Sessions Australia with Daisy Wong, Head of Security Awareness at Medibank

    CISO Reality: Record Pay, Rising Pressure, and Retention Risk

    Originally published on January 8, 2026 by CSO Online.

    Expert Analysis for Orange County Businesses

    How this impacts SMBs in Southern California

    Tech News Roundup: Holes in Veeam Backup suite allow remote code execution, creation of malicious backup config files.

    The recent discovery of vulnerabilities in Veeam’s Backup & Replication suite highlights a critical issue for small and medium businesses (SMBs) in Orange County and Southern California. With four security flaws that allow for potential remote code execution, local businesses relying on Veeam for their backup solutions must prioritize immediate action. Although Veeam has released a patch, the implications of these vulnerabilities underscore the need for tighter access controls and rigorous monitoring of backup environments. Given the increasing sophistication of cyber threats, especially from ransomware actors targeting backup systems, it’s imperative that SMBs remain vigilant and proactive in their cybersecurity practices.

    At The Network Company, we understand the unique challenges faced by local businesses regarding cybersecurity and data protection. Our managed IT services include comprehensive assessments of your backup solutions, ensuring that access rights are properly managed and that alerts are set up for unusual activities. Moreover, our BCDR (Backup and Disaster Recovery) services can help you maintain a resilient backup strategy, enabling quick recovery in the face of unexpected incidents. Don’t wait for a breach to occur; consider auditing your systems today and contact us to discuss how we can enhance your managed services and cloud backup strategies for a more secure future.

    Read the full article: Original Source Link

    Frequently Asked Questions

    What are the vulnerabilities in Veeam Backup Suite?

    The vulnerabilities allow remote code execution and unauthorized file modifications by users with specific roles.

    How can I secure my Veeam Backup configurations?

    Install the latest patch, audit your backup configurations, and monitor backup jobs actively.

    Content Quality

    Last Reviewed:January 8, 2026
    Fact-Checked:January 8, 2026
    0
    Word Count:1,162 words

    Article Tags

    Security, Vulnerabilities
    Veeam Backup vulnerabilities
    remote code execution Veeam
    CVE-2025-59470
    Veeam Backup patch
    backup configuration security
    cybersecurity vulnerabilities
    Veeam Backup & Replication
    data protection best practices
    backup system security threats
    IT security updates
    Veeam Backup user roles
    malicious configuration files
    C

    About Cybersecurity at the edge: Securing rugged IoT in mission-critical environments | CSO Online

    Content Author

    Cybersecurity expert with extensive experience in protecting critical systems and data. Specializes in identifying vulnerabilities and implementing robust security measures in backup solutions.

    Expertise: Cybersecurity, Vulnerability Management, IT Security, Data Protection, Backup Solutions

    Related Articles

    Meet Fragnesia, the third Linux kernel vulnerability in a month
    Security, Vulnerabilities

    Meet Fragnesia, the third Linux kernel vulnerability in a month

    Linux admins reeling from handling last month’s CopyFail and last week’s Dirty Frag kernel vulnerabilities have a new headache to deal with: Fragnesia. “This is a significant vulnerability,” Robert Beggs, head of incident response firm DigitalDefence, told CSO. “It is bypassing traditional filesystem permissions that are present and enforced (for example, ‘file is owned by root’, or ‘file is read-only’) to allow manipulation without touching the disk.” Similar to Dirty Frag, Fragnesia (CVE-2026-46300) is a local privilege escalation hole that exploits a vulnerability in the XFRM ESP-in-TCP subsystem to achieve a memory write primitive in the kernel. XFRM is an IP framework intended for packet transformations, and ESP-in-TCP (Encapsulating Security Payload in TCP) is a networking technique used to encapsulate IPsec ESP packets inside TCP segments. A proof of concept (PoC) exploit is already publicly available. The good news, Beggs said, is that the vulnerability can’t be exploited remotely. An attacker needs local access to trigger specific code paths and be able to control local socket operations and manipulate packet fragmentation. Still, he added, any unprivileged user can exploit the bug on a vulnerable system to corrupt security-sensitive files in memory, such as privileged access management configuration, password, systemd service files, or cron jobs. Although the attacker cannot modify the file on the disk, modifying in-memory files can trick privileged processes, alter system behavior, execute arbitrary code, and escalate privileges on the system, he said. Linux distributions including Red Hat, Ubuntu, AlmaLinux and others are pushing out patches or mitigations; CloudLinux said a patch is being tested. In a statement to CSO, Mike McGrath, Red Hat’s vice-president of Core Platforms, said issuing mitigations and fixes for privilege escalations like Fragnesia are a top priority. “We have published workarounds for the esp4 and esp6 kernel modules that we feel provide protection to customers in the immediate term while we work with the upstream community to identify a permanent fix in the form of a patch,” he said. According to Linux support provider TuxCare, systems running the affected skbuff code paths, including kernels that have already received the Dirty Frag fix, are impacted. The public PoC requires systems with the configuration option CONFIG_INET_ESPINTCP to access the bug, so kernels built without it block this exploit. But the underlying skbuff defect may be reachable through other paths. Microsoft urges Linux users and organizations to apply the patch as soon as possible by running update tools. If patching is not possible at this point, consider applying the same mitigations as for Dirty Frag, such as assessing whether esp4, esp6, and related xfrm/IPsec functionality can be temporarily disabled safely, restricting unnecessary local shell access, hardening containerized workloads, and increasing monitoring for abnormal privilege escalation activity. Related content: Kill switch for Linux kernel features proposed to improve security Beggs advises system administrators to confirm kernel exposure by reviewing version numbers, and then update to a patched kernel if necessary and reboot the affected system. If ESP-in-TCP is not required, disable the module and block its use; this mitigation can also be immediately applied until patching is complete. Because the vulnerability requires local access, make sure that basic steps such as enforcing MFA for privileged accounts, disabling of unneeded shell access, and enforcing least privilege are all in place. Beggs also said admins may wish to increase monitoring of privileged processes (PAM, systemd, cron) and look for unexpected restarts, unexpected config reloads, and sudden privilege escalations.

    Veeam warns admins to patch now as critical RCE flaws hit Backup & Replication
    Security, Vulnerabilities

    Veeam warns admins to patch now as critical RCE flaws hit Backup & Replication

    Backup vendor Veeam has released security updates to patch multiple vulnerabilities in its widely used Backup and Replication platform, including three critical flaws that could allow authenticated users to execute code on backup servers. Detailed in the company’s advisory KB4830, the vulnerabilities affect Veeam Backup & Replication 12.3.2.4165 and earlier version 12 builds, with fixes now available in build 12.3.2.4465. The disclosure covers five security issues in total, including three remote code execution (RCE) bugs and two high-severity vulnerabilities enabling file manipulation or privilege escalation. Each of the three critical flaws carries a CVSS score of 9.9 out of 10 and allows authenticated users to execute code on backup infrastructure components under certain conditions. Backup systems have become increasingly valuable targets for attackers, particularly ransomware operators, because compromising them can undermine recovery capabilities and enable data destruction or exfiltration at scale. Flaws allow privilege escalation and RCE The most serious issues addressed in the advisory are the RCE bugs that an authenticated domain user can exploit to execute code on the Veeam Backup Server or associated components. In practice, this means an attacker who already has some level of access within the environment, such as through compromised credentials, could leverage the flaws to take control of backup infrastructure. The three bugs are tracked as CVE-2026-21666, CVE-2026-21667, and CVE-2026-21708. The advisory also details two high-severity flaws. CVE-2026-21668 allows attackers with repository access to manipulate arbitrary files on backup infrastructure, potentially affecting stored backup data, and CVE-2026-21672, a local privilege escalation flaw, could enable attackers who already have limited access to elevate their privileges on the Veeam servers. The advisory said that some vulnerabilities were reported through Veeam’s bug bounty program on HackerOne, while others were discovered during internal testing. While Veeam did not mention any in-the-wild exploitation, the Backup and Replication bugs have been repeatedly weaponized in the past. Patches are available Veeam warned that organizations should apply the patched build promptly, noting that vulnerability disclosures frequently trigger attempts by attackers to reverse-engineer patches and develop exploits for unpatched systems. The issues were fixed in Veeam Backup & Replication 12.3.2.4465, and organizations running unsupported or older builds should assume they are vulnerable and upgrade immediately. The urgency around the latest bugs is amplified by the fact that Veeam Backup & Replication has repeatedly faced critical vulnerabilities in recent years, some of which have been actively exploited by attackers. In 2024, security agencies warned that ransomware groups were exploiting CVE-2024-40711, a critical flaw in the platform that allowed remote code execution without authentication. Attackers used the vulnerability to compromise backup servers and delete recovery data as part of ransomware campaigns. The pattern continued in 2025, when Veeam patched CVE-2025-23120, another critical RCE bug that allowed any authenticated domain user to execute code on a backup server in domain-joined environments. The steady stream of high-severity bugs, along with the history of real-world exploitation, makes timely patching critical for organizations running Veeam Backup & Replication. Organizations must treat backup systems as highly privileged infrastructure requiring strong access controls and isolation.

    Flaws in four popular VS Code extensions left 128 million installs open to attack
    Security, Vulnerabilities

    Flaws in four popular VS Code extensions left 128 million installs open to attack

    Critical and high-severity vulnerabilities were found in four widely used Visual Studio Code extensions with a combined 128 million downloads, exposing developers to file theft, remote code execution, and local network reconnaissance. Application security company OX Security published the findings this week, saying it had begun notifying vendors in June 2025 but received no response from three of the four maintainers. Three CVEs, CVE-2025-65717, CVE-2025-65715, and CVE-2025-65716, were formally assigned and published on February 16. VS Code extensions are add-ons that expand the functionality of Microsoft’s widely used code editor, adding capabilities such as language support, debugging tools, live preview, and code execution. They run with broad access to local files, terminals, and network resources, which is what made these vulnerabilities consequential. Unlike the rogue extensions that threat actors have repeatedly planted in the VS Code marketplace, these flaws resided in legitimate, widely installed tools, meaning developers had no reason to suspect them, OX Security said in an advisory. “Our research demonstrates that a hacker needs only one malicious extension, or a single vulnerability within one extension, to perform lateral movement and compromise entire organizations,” the advisory added. The vulnerabilities also affected Cursor and Windsurf, the AI-powered IDEs built on VS Code’s extension infrastructure. OX Security published individual advisories for each flaw, detailing how each could be exploited and what an attacker could achieve. How the attacks worked The most severe flaw, CVE-2025-65717 (critical), was in Live Server, a 72-million-download extension that launches a local HTTP server for real-time browser previews. OX Security found the server was reachable from any web page a developer visited while it was running, not just their own browser. “Attackers only need to send a malicious link to the victim while Live Server is running in the background,” OX Security researchers Moshe Siman Tov Bustan and Nir Zadok wrote in an advisory. CVE-2025-65715 (high severity) affected Code Runner, with 37 million downloads. The extension reads execution commands from a global configuration file, and OX Security found a crafted entry that was enough to trigger arbitrary code execution, including reverse shells. An attacker could place it by phishing a developer into pasting a malicious snippet, or through a compromised extension that modified the file silently. CVE-2025-65716 (CVSS 8.8) affected Markdown Preview Enhanced, with 8.5 million downloads. Simply opening an untrusted Markdown file was enough to trigger it. “A malicious Markdown file could trigger scripts or embedded content that collects information about open ports on the victim’s machine,” the researchers noted. Microsoft quietly patched its own extension The fourth vulnerability played out differently. Microsoft’s Live Preview extension, with 11 million downloads, contained a cross-site scripting flaw that, according to OX Security, let a malicious web page enumerate files in the root of a developer’s machine and exfiltrate credentials, access keys, and other secrets. The researchers reported the issue to Microsoft on August 7. Microsoft initially rated it as low severity, citing required user interaction. “However, on September 11, 2025 — without notifying us — Microsoft quietly released a patch addressing the XSS security issues we reported. We only recently discovered that this patch had been deployed,” the researchers added. No CVE was assigned to this vulnerability. “Users with Live Preview installed should update to version 0.4.16 or later immediately,” the researchers suggested. Microsoft did not immediately respond to a request for comment. Taken together, the four flaws pointed to a broader problem with how developer tools are secured and maintained. What security teams should do “These vulnerabilities confirm that IDEs are the weakest link in an organization’s supply chain security,” the researchers at OX Security said in the advisory. Developer workstations routinely hold API keys, cloud credentials, database connection strings, and SSH keys. OX Security warned that a successful exfiltration from a single machine could give an attacker access to an organization’s broader infrastructure and that the risks extended to lateral movement and full system takeover. The researchers advised developers to disable extensions not actively in use and avoid browsing untrusted sites while localhost servers are running. They also cautioned against applying configuration snippets from unverified sources to VS Code’s global settings.

    Ready to Transform Your Business?

    Discover how our expert IT solutions can help your business thrive.