Sereal::Decoder versions from 4.000 through 4.009_002 for Perl embeds a vulnerable version of the Zstandard library.
Sereal::Decoder embeds a version of the Zstandard (zstd) library that is vulnerable to CVE-2019-11922. This is a race condition in the one-pass compression functions of Zstandard prior to version 1.3.8 could allow an attacker to write bytes out of bounds if an output buffer smaller than the recommended size was used.
UnQLite versions through 0.06 for Perl uses a potentially insecure version of the UnQLite library.
UnQLite for Perl embeds the UnQLite library. Version 0.06 and earlier of the Perl module uses a version of the library from 2014 that may be vulnerable to a heap-based overflow.
Compress::Raw::Zlib versions through 2.219 for Perl use potentially insecure versions of zlib.
Compress::Raw::Zlib includes a copy of the zlib library. Compress::Raw::Zlib version 2.220 includes zlib 1.3.2, which addresses findings fron the 7ASecurity audit of zlib. The includes fixs for CVE-2026-27171.
CVE-2026-0943 is a high-severity vulnerability in HarfBuzz::Shaper versions prior to 0.032 for Perl, caused by a null pointer dereference in a bundled HarfBuzz library (version 8.4.0 or earlier). This flaw leads to a denial of service (DoS) condition without requiring authentication or user interaction. The vulnerability stems from a dependency on a vulnerable third-party component, specifically HarfBuzz affected by CVE-2026-22693. Although no known exploits are currently in the wild, the vulnerability's ease of remote exploitation and impact on availability make it a significant risk. European organizations using affected versions in their software stacks, especially those relying on Perl bindings for text shaping or rendering, should prioritize patching or mitigating this issue. Countries with strong software development sectors and extensive use of open-source libraries are more likely to be impacted. Immediate mitigation involves updating to HarfBuzz::Shaper version 0.
CVE-2025-69275 is a high-severity vulnerability in Broadcom DX NetOps Spectrum (version 24.3.9 and earlier) caused by a dependency on a vulnerable third-party component leading to DOM-based Cross-Site Scripting (XSS). The flaw allows an attacker to execute malicious scripts in the context of the affected application without requiring user interaction or authentication, though exploitation complexity is high. This vulnerability impacts confidentiality and integrity by potentially exposing sensitive data or enabling unauthorized actions within the management platform. European organizations using DX NetOps Spectrum for network monitoring and management are at risk, especially those in critical infrastructure sectors. No known exploits are currently in the wild, but the vulnerability’s presence in widely deployed network operations software necessitates prompt mitigation. Mitigation involves updating to a patched version once available, applying strict input validation and content security policies, and monitoring network traffic for suspicious activity. Countries with significant Broadcom DX NetOps Spectrum deployments and critical infrastructure reliance, such as Germany, France, the UK, and the Netherlands, are most likely to be affected. Given the CVSS 4.
Forcepoint One DLP Client, version 23.04.5642 (and possibly newer versions), includes a restricted version of Python 2.5.4 that prevents use of the ctypes library.ctypes is a foreign function interface (FFI) for Python, enabling calls to DLLs/shared libraries, memory allocation, and direct code execution. It was demonstrated that these restrictions could be bypassed.
CVE-2025-15444 is a critical vulnerability in the Crypt::Sodium::XS Perl module, which depends on a vulnerable version of libsodium (<= 1.0.20). The underlying libsodium flaw (CVE-2025-69277) mishandles validation of elliptic curve points in certain cryptographic operations, potentially allowing invalid points that compromise cryptographic guarantees. This can lead to severe impacts on confidentiality, integrity, and availability without requiring authentication or user interaction. The vulnerability affects all versions of Crypt::Sodium::XS prior to 0.000042, which updates libsodium to a fixed version released January 3, 2026. European organizations relying on this module for cryptographic functions in Perl applications are at risk, especially in sectors handling sensitive data or critical infrastructure. Mitigation requires immediate upgrading to Crypt::Sodium::XS version 0.000042 or later and auditing dependent applications for use of vulnerable libsodium versions.
A security issue was found in the IPv6 stack in the Micro850 and Micro870 controllers when the controllers received multiple malformed packets during fuzzing. The controllers will go into recoverable fault with fault code 0xFE60. To recover the controller, clear the fault.
Weblate is a web based localization tool. An open redirect exists in versions 5.13.2 and below via the redir parameter on .within.website when Weblate is configured with Anubis and REDIRECT_DOMAINS is not set. An attacker can craft a URL on the legitimate domain that redirects a victim to an attacker-controlled site. The redirect can also be used to initiate drive-by downloads (redirecting to a URL that serves a malicious file), increasing the risk to end users. This issue is fixed in version 5.13.3.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.1002 and Application versions prior to 20.0.2614 (VA and SaaS deployments) contain multiple Docker containers that include outdated, end-of-life, unsupported, or otherwise vulnerable third-party components (examples: Nginx 1.17.x, OpenSSL 1.1.1d, various EOL Alpine/Debian/Ubuntu base images, and EOL Laravel/PHP libraries). These components are present across many container images and increase the product's attack surface, enabling exploitation chains when leveraged by an attacker. Multiple distinct EOL versions and unpatched libraries across containers; Nginx binaries date from 2019 in several images and Laravel versions observed include EOL releases (for example Laravel 5.5.x, 5.7.x, 5.8.x). This vulnerability has been identified by the vendor as: V-2024-014 — Outdated Dependencies.
Dependency on Vulnerable Third-Party Component (CWE-1395) in the PostgreSQL backend in AxxonSoft Axxon One (C-Werk) 2.0.8 and earlier on Windows and Linux allows a remote attacker to escalate privileges, execute arbitrary code, or cause denial-of-service via exploitation of multiple known CVEs present in PostgreSQL v10.x, which are resolved in PostgreSQL 17.4.
SAP NetWeaver AS Java application uses Adobe Document Service, installed with a vulnerable version of OpenSSL.Successful exploitation of known vulnerabilities in the outdated OpenSSL library would allow user with high system privileges to access and modify system information.This vulnerability has a low impact on confidentiality and integrity, with no impact on availability.
Net::Dropbear versions through 0.16 for Perl contains a dependency that may be susceptible to an integer overflow.
Net::Dropbear embeds a version of the libtommath library that is susceptible to an integer overflow associated with CVE-2023-36328.
CryptX for Perl before version 0.065 contains a dependency that may be susceptible to malformed unicode.
CryptX embeds the tomcrypt library. The versions of that library in CryptX before 0.065 may be susceptible to CVE-2019-17362.
Perl CryptX before version 0.087 contains a dependency that may be susceptible to an integer overflow.
CryptX embeds a version of the libtommath library that is susceptible to an integer overflow associated with CVE-2023-36328.
A buffer overflow, as described in CVE-2020-8927, exists in the embedded Brotli library. Versions of IO::Compress::Brotli prior to 0.007 included a version of the brotli library prior to version 1.0.8, where an attacker controlling the input length of a "one-shot" decompression request to a script can trigger a crash, which happens when copying over chunks of data larger than 2 GiB. It is recommended to update your IO::Compress::Brotli module to 0.007 or later. If one cannot update, we recommend to use the "streaming" API as opposed to the "one-shot" API, and impose chunk size limits.