09/29/2026, 19.33
by Lorenzocovers images, design and visual AI
Condividi su Facebook Condividi su Twitter Condividi su Pinterest Condividi su Telegram Condividi su WhatsApp

Critical Security Flaws Hit Apache, GitLab and PaperCut Systems

New security alerts reveal critical vulnerabilities in Apache Tomcat, GitLab, and PaperCut, exposing businesses to remote code execution and data leaks.
Critical Security Flaws Hit Apache, GitLab and PaperCut Systems
Key points
  • Apache Tomcat faces 15 vulnerabilities, including 4 critical flaws allowing security bypass and DoS.
  • GitLab CE/EE updates resolve 7 vulnerabilities that could lead to unauthorized information disclosure.
  • PaperCut NG/MF software is susceptible to remote code execution via high-severity flaws.
  • Immediate patching is required across these platforms to prevent arbitrary code execution by remote actors.

The digital infrastructure supporting modern enterprise operations is currently facing a wave of critical security threats. Recent alerts from the Italian National Cybersecurity Agency (ACN) have highlighted a series of severe vulnerabilities affecting some of the most widely used software tools in the corporate world, ranging from web server environments and version control systems to print management software.

For business owners and CTOs, these alerts represent more than just technical patches; they signify a systemic risk where a single unpatched server or a legacy print manager can become an entry point for malicious actors to seize control of internal networks.

The Apache Tomcat Crisis: High Systemic Impact

One of the most concerning reports involves Apache Tomcat and Apache Tomcat Native. The scale of the vulnerability is significant, with 15 security flaws identified. Among these, four are classified as critical and nine as high severity. The potential consequences for an organization are severe: attackers could bypass security restrictions, manipulate HTTP request content, or trigger a Denial of Service (DoS) to crash essential services.

The vulnerability spans multiple versions, including Tomcat 9.0.x, 10.1.x, and 11.0.x. However, the most dangerous position is held by companies still relying on Tomcat 7.0.x and 8.5.x. These versions are no longer supported, meaning no corrective updates will be released for them. For these legacy systems, the only viable path to security is a complete migration to a supported branch. The systemic impact of these flaws is rated as high, reflecting the ubiquity of Apache Tomcat in hosting Java-based web applications globally.

To mitigate these risks, administrators must prioritize updates to the latest versions, specifically 9.0.122, 10.1.60, and 11.0.26, or the respective Native versions 1.3.9 and 2.0.16. More details on these alerts can be found via the ACN security portal.

GitLab Vulnerabilities and the Risk of Data Leaks

Simultaneously, GitLab Community Edition (CE) and Enterprise Edition (EE) have been hit by seven vulnerabilities. While the number is lower than in the Apache case, the severity remains alarming, with two critical and one high-severity flaw. These gaps in security could allow a remote attacker to gain access to confidential information or execute arbitrary code on the affected systems.

The affected versions are extensive, covering 19.2.x (prior to 19.2.7), 19.3.x (prior to 19.3.3), 19.4.x (prior to 19.4.1), and virtually all versions dating back to 13.11. Because GitLab often houses the intellectual property of a company in the form of source code, an information disclosure vulnerability is particularly catastrophic. It does not just risk the availability of the service but the very secrets that give a business its competitive edge.

The recommended action is an immediate update to the latest patched versions. The systemic impact for GitLab is also rated as high, emphasizing that version control systems are prime targets for industrial espionage and supply chain attacks.

PaperCut NG/MF and the Danger of Remote Code Execution

While web servers and code repositories often take center stage, the vulnerability in PaperCut NG/MF serves as a reminder that peripheral corporate software can be just as dangerous. PaperCut, used globally for print management and monitoring in corporate environments, has revealed three security vulnerabilities, two of which are rated as high severity.

The primary threat here is Remote Code Execution (RCE). If exploited under specific conditions, a remote attacker could execute arbitrary code on the systems running PaperCut. This effectively turns a print server into a beachhead for further lateral movement within the corporate network.

The affected versions include PaperCut NG/MF 26.x (version 26.0.4 and earlier) and 25.x (version 25.0.12 and earlier). Unlike the Apache situation, where some versions are obsolete, the PaperCut flaws affect relatively recent releases, making prompt updates essential for all users of the software. You can find the specific alert regarding this software here.

Analyzing the Pattern of Modern Exploits

When looking at these three distinct cases, a clear pattern emerges. The most dangerous vulnerabilities are those that allow Remote Code Execution (RCE) or Security Restriction Bypass. These are the gold standards for hackers because they provide the highest level of control with the least amount of initial access.

The common thread across these alerts is the critical nature of the software involved; they are not optional tools but foundational elements of the corporate IT stack.

The systemic impact ratings provided by the ACN—ranging from medium for PaperCut to high for Apache and GitLab—provide a roadmap for prioritization. A high systemic impact means that the software is widely deployed across critical infrastructure, meaning a single exploit could have a domino effect across thousands of companies globally.

Strategic Mitigation for Enterprise IT

Addressing these vulnerabilities requires more than just clicking an update button. It requires a structured approach to patch management. Many organizations fail not because a patch doesn't exist, but because they lack the visibility to know which versions of which software are running on which servers.

The current situation demands a three-step response:

First, a comprehensive audit of the environment to identify all instances of Apache Tomcat, GitLab, and PaperCut. Second, the immediate application of vendor-supplied patches for supported versions. Third, the urgent decommissioning or migration of end-of-life (EOL) software, such as Tomcat 7.0.x and 8.5.x, which can no longer be secured through updates.

Global Implications for US and UK Businesses

For entrepreneurs and business leaders in the USA and the UK, these alerts are a wake-up call regarding the fragility of the global software supply chain. While the alerts originated from a European agency, the software involved is agnostic to borders. A vulnerability in Apache Tomcat affects a server in London just as much as one in New York or Rome.

In the United States, the focus on cybersecurity is increasingly shifting toward mandatory disclosure and stricter standards for software transparency. The CISA (Cybersecurity and Infrastructure Security Agency) often echoes these types of warnings, urging companies to move toward a Zero Trust architecture. In the UK, the NCSC (National Cyber Security Centre) emphasizes the danger of legacy systems—a point perfectly illustrated by the unsupported Apache Tomcat versions mentioned in these reports.

From a regulatory perspective, failing to patch known critical vulnerabilities can be seen as a lack of due diligence. In the event of a data breach, regulators in both the US and UK are increasingly looking at whether the company followed industry-standard patching cycles. If a breach occurs via a vulnerability that had a known patch available for weeks, the legal and financial penalties for negligence are significantly higher.

Furthermore, for companies operating across borders, the alignment of security standards is becoming a business necessity. Whether it is complying with the GDPR in Europe or various state-level privacy laws in the US, the technical baseline remains the same: keep your core infrastructure updated or risk total systemic compromise.

FAQ

Which versions of Apache Tomcat are the most at risk?

Versions 7.0.x and 8.5.x are the most critical because they are no longer supported and cannot be patched, requiring a full migration to a newer version.

What is the main risk associated with the PaperCut vulnerability?

The primary risk is Remote Code Execution (RCE), which allows a remote attacker to run arbitrary code on the system.

How should a company handle the GitLab vulnerabilities?

Companies should immediately update to the latest versions (e.g., 19.2.7, 19.3.3, or 19.4.1) to prevent unauthorized information disclosure and RCE.

Why is the systemic impact rated as high for Apache and GitLab?

Because these tools are foundational to web hosting and software development, meaning a flaw in them can affect a vast number of organizations and critical services globally.


Sources: Acn (7) ·

Hai una domanda su questo dossier?

Scrivila qui: Susanna, l assistente AI di glacom, ti risponde via email con un approfondimento gratuito.

Nessuna consulenza personalizzata (finanziaria, legale o medica): solo informazione e fonti. Email usata solo per rispondere.

oppure scrivile su: WhatsApp · Telegram · SimpleX · Delta Chat · Email

Condividi su Facebook Condividi su Twitter Condividi su Pinterest Condividi su Telegram Condividi su WhatsApp
Printable version
CLOSE X
See also
Critical Vulnerabilities Hit Oracle, Dell, and PHP: Global Risk Alert
Major security flaws in Oracle, Dell, and PHP components expose global enterprises to RCE and SQL injection. Learn the risks and necessary mitigation …
16/11/2026 12:04
Ollama Critical Vulnerability: RCE Risk in Local AI Deployment
A critical Path Traversal vulnerability (CVE-2026-103663) in Ollama allows remote code execution. Learn the risks for local LLM deployments and how to…
12/11/2026 12:25
Critical Security Flaws Hit Mozilla, MongoDB, and ASUS Infrastructure
New security alerts reveal critical vulnerabilities in Mozilla browsers, MongoDB C# drivers, and ASUS routers, demanding immediate corporate patching.
10/11/2026 16:37
Critical Security Flaws Hit Fortinet, MongoDB and Stormshield
New critical vulnerabilities in Fortinet, MongoDB, and Stormshield expose firms to remote code execution and auth bypass. Learn the risks and fixes.
07/11/2026 07:53
Binance $6.3 Billion Hack: EIP-7702 Exploit and DevOps Breach
A massive $6.3 billion breach hits Binance via an EIP-7702 delegation exploit. Discover how a compromised laptop led to the largest crypto theft in hi…
31/10/2026 11:47