Complete feed
Security advisories & CVEs
355 advisories across 32 monitored vendors.
Android app · Google Play
Take your CVE monitoring with you.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Advisory [CVE-2024-40709] List of Security Fixes and Improvements in Veeam Agent for Linux
List of Security Fixes and Improvements in Veeam Agent for Linux KB ID: 3109 Product: Published: 2020-03-02 Last Modified: 2026-08-21 Purpose 13.1.0.252 - OpenSSL upgraded to version 3.5.7 13.0.1.404 - The port range opened on the host firewall was changed to 2500-3300. 13.0.3.213 13.0.1.94 13.0.0.0.772 6.3.2.1307 6.2.0.101 - CVE-2024-40709 vulnerability was fixed. 6.1.0.1498 - OpenSSL library updated to 1.0.2zi. - LZ4 library updated to 1.9.4. - Updated zlib library to 1.2.13. - Stronger backup encryption. - (See pg. 7 of Veeam Backup & Replication 12.1 What's New PDF ) 6.0.2.1168 5.0.2.4707 - liblz4 was updated to v1.9.4. - zlib was updated to v1.2.13. - PuTTY was updated to 0.80. 5.0.0.4318 - Addressed an issue with insecure default permissions of files created in /tmp 4.0.1.2365 - Sensitive information used by managed Linux agent may get logged in the Linux operating system logs. - Creating an SMB repository using CLI command causes plain text password to be logged in the Veeam debug log. 4.0.0.1961 - An issue of insecure file permissions was addressed (vulnerability reported by RACK911 Labs). - OpenSSL was updated to version 1.0.2t. As we're establishing this new process, we appreciate any feedback on the content or format of this KB article. Please let us know in the corresponding topic on the Veeam Community Forums.
Advisory [CVE-2026-58074 +2] Release Information for Veeam ONE 12 and Updates
Release Information for Veeam ONE 12 and Updates KB ID: 4705 Product: Published: 2024-12-23 Last Modified: 2026-08-25 Veeam ONE v12 Releases 12.3.0.7165 What's New Veeam ONE 12.3 Patch 1 is a cumulative maintenance and security update for Veeam ONE 12.3. It resolves reported issues across reporting, monitoring, alarms, licensing, and integrations, adds REST API and ServiceNow enhancements, and addresses externally reported security vulnerabilities. Applying this patch is recommended for all Veeam ONE 12.3 deployments. New Features and Improvements Cloud Backup Sizes in the REST API The public REST API now reports the size of cloud backups and of their restore points. AWS Account Identification Veeam ONE now collects the AWS Account ID and account alias for workloads protected by Veeam Backup for AWS, and the public REST API returns both for protected Amazon EC2 workloads. Customizable ServiceNow Short Description Resolved Issues - Veeam ONE repeatedly logs an error because triggered alarms are not synchronized correctly between the alarm cache and the database: Cannot insert the value NULL into column 'triggered_alarm_id' - The Backup Copy RPO alarm reports incorrect information because deleted backup copy workers are still taken into account. - The Backup Job State alarm does not raise a Warning when a backup job session finishes with a warning.
Critical [CVE-2025-30177 +1] Improper input validation vulnerability in Apache Camel Undertow component
Improper input validation vulnerability in Apache Camel Undertow component. This issue affects Apache Camel: from 4.11.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. UndertowEndpoint defaulted its headerFilterStrategy field to the base HttpHeaderFilterStrategy and pushed that instance into the UndertowHttpBinding it creates lazily, overwriting the UndertowHeaderFilterStrategy that DefaultUndertowHttpBinding installs in its own constructor. Unless a deployment supplied a custom binding or an explicit headerFilterStrategy, the undertow-specific filtering therefore never executed on endpoint-configured routes: the strategy object was constructed and immediately replaced before it could be consulted. The consequence is that the legacy websocket. Exchange-header prefix was not filtered at the undertow transport boundary in either direction, so an undertow HTTP consumer mapped inbound wire headers of that form onto the Exchange, where an undertow WebSocket producer reads them as dispatch directives and can be made to deliver to a peer other than the one the route selected; and header names that undertow itself does not accept were mapped onto the Exchange rather than being skipped. Rest DSL consumers were never affected, because UndertowComponent assigns UndertowRestHeaderFilterStrategy explicitly, which extends the undertow strategy.
Critical [CVE-2026-55993 +1] Improper input validation vulnerability in Apache Camel Atmosphere Websocket component
Improper input validation vulnerability in Apache Camel Atmosphere Websocket component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-atmosphere-websocket producer selects which connected WebSocket peers a message is delivered to through Exchange headers, and the string values of those headers sat outside the Camel namespace: websocket.connectionKey and websocket.connectionKey.list, along with websocket.sendToAll, websocket.eventType and websocket.errorType. WebsocketEndpoint extends ServletEndpoint and so inherits HttpHeaderFilterStrategy, which filters only the Camel and camel prefixes; the dotted names therefore fell outside the filtered namespace and were admitted in both directions by every HTTP-family consumer. In a route bridging an HTTP consumer into an atmosphere-websocket producer, an external sender could supply the list header and take over the producer's dispatch decision. WebsocketProducer.process tests the list header before the single-key header, so an injected value discarded the recipient the route had selected: a notification intended for one connected client could be suppressed, or delivered instead to a different client whose connection key the sender knows.
Critical [CVE-2026-66906] Relative path traversal vulnerability in Apache Camel Azure Storage Blob component
Relative path traversal vulnerability in Apache Camel Azure Storage Blob component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-azure-storage-blob component can download an Azure Storage blob to the local filesystem through its download BlobToFile operation, writing into the directory named by the fileDir endpoint option, which is documented as usable from both the producer and the consumer. BlobOperations.download BlobToFile built the local target by joining fileDir with the remote blob name exactly as the Azure SDK reported it (new File(fileDir, client.getBlobName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The blob name is not route-controlled data: the consumer enumerates the container in BlobConsumer.createBatchExchangesFromContainer, which lists blobs and creates one exchange per entry from BlobItem.getName() verbatim, applying no name filtering by default. A blob name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the consumed container cause Camel to create or overwrite a file at a location of their choosing, with the privileges of the Camel process.
High [CVE-2026-76098] Denial of Service via excessive emphasis markers in Markdown
Denial of Service via excessive emphasis markers in Markdown. Red Hat rates this important (CVSS 7.5). Weakness: CWE-770. Affected products named by the advisory: Migration Toolkit for Applications 8; Red Hat OpenShift AI (RHOAI); Red Hat OpenShift Container Platform 4.
High [CVE-2026-78465] Gimp: integer overflow in pcx loader (planes=4) leads to heap overflow on 32-bit
A flaw was found in the file-pcx plugin in GIMP, affecting 32-bit builds only. When processing a PCX image file, the plugin calculates memory allocation sizes based on the image dimensions and the number of color planes. If a crafted file sets the number of planes to 4 alongside sufficiently large dimensions, the calculation exceeds the 32-bit integer limit and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when the plugin subsequently writes image data into the undersized buffer, causing memory corruption, potentially leading to arbitrary code execution or a denial of service. To exploit this vulnerability, an attacker needs to convince a user to process a specially crafted PCX image with GIMP, reducing the likelihood of exploitation. However, successful exploitation may potentially lead to arbitrary code execution or a denial of service. Default Red Hat Enterprise Linux security features, including SELinux enforcement, Address Space Layout Randomization (ASLR) and NX (No-Execute) stack protection, significantly increase the difficulty of achieving arbitrary code execution, limiting the impact of this vulnerability. Due to this reason, this flaw has been rated with an important severity. Red Hat severity: Important — CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
High [CVE-2026-66908] Improper Authentication vulnerability in Apache Camel Platform HTTP Main component
Improper Authentication vulnerability in Apache Camel Platform HTTP Main component. This issue affects Apache Camel: from 4.8.0 before 4.22.0. The camel-main embedded HTTP server can protect its endpoints with JWT authentication, configured through authenticationEnabled together with the JWT keystore properties. JWTAuthenticationConfigurer.buildJwtOptions returned null when neither jwtIssuer nor jwtAudience was configured, and the caller then skipped the JWTAuthOptions.setJWTOptions call entirely, so the Vert.x JWTAuth instance was built from the keystore alone. The result was that inbound tokens were checked only for signature and expiry: the iss and aud claims were not validated at all. Nothing signalled this - the server started normally and reported no warning - so a deployment configured the documented way silently enforced less than the operator believed it had enabled, and the component documentation itself presented signature and expiry checking as the default with issuer and audience as an optional extra. Both the application server and the management server were affected, because the omission was in each of the two configureAuthentication paths. Any unexpired token signed by any key the configured keystore trusts was therefore accepted, regardless of which issuer minted it or which audience it was intended for.
High [CVE-2026-66907] Relative path traversal vulnerability in Apache Camel Google Storage component
Relative path traversal vulnerability in Apache Camel Google Storage component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-google-storage consumer downloads Google Cloud Storage objects to the local filesystem when the download FileName option is set. That option is documented as a folder or a filename, and when its value contains no expression token the consumer builds the local destination by appending the object name to it: evaluateFileExpression sets the Exchange file-name header to the remote object name and evaluates download FileName + "/${file:name}". The ${file:name} token returns the file-name header verbatim, unlike ${file:onlyname}, which applies FileUtil.stripPath to it. The resulting string was passed directly to new File(result) and blob.download To(file.toPath()) with no lexical normalization and no check that the destination stayed inside the configured directory. The object name is not route-controlled data: the consumer lists the bucket, iterates every returned blob and creates one exchange per object from blob.getBlobId().getName() verbatim, and the filter option that could restrict those names is not applied at all unless it has been explicitly set.
High [CVE-2025-9615 +1] 802-1x ca-path and phase2-ca-path bypass private_user restriction, allowing WPA-Enterprise server validation bypass (incomplete fix for CVE-2025-9615)
802-1x ca-path and phase2-ca-path bypass private_user restriction, allowing WPA-Enterprise server validation bypass (incomplete fix for CVE-2025-9615). Red Hat rates this important (CVSS 7.1). Weakness: CWE-863. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat package: networkmanager.
High [CVE-2026-71366] notification backends allow SSRF and credential leakage
notification backends allow SSRF and credential leakage. Red Hat rates this important (CVSS 7.7). Weakness: CWE-918. Red Hat lists fixing advisory RHSA-2026:59153 with package automation-controller-0:4.7.16-1.el9ap, ansible-automation-platform-26/controller-rhel9:1787244009, automation-controller-0:4.6.32-1.el8ap, ansible-automation-platform-27/controller-rhel9:1787220257. Affected products named by the advisory: Red Hat Ansible Automation Platform 2.5 for RHEL 8; Red Hat Ansible Automation Platform 2.5 for RHEL 9; Red Hat Ansible Automation Platform 2.6 for RHEL 9; Red Hat Ansible Automation Platform 2.7.
High [CVE-2026-71364] project archive extraction allows path traversal file writes
project archive extraction allows path traversal file writes. Red Hat rates this important (CVSS 7.2). Weakness: CWE-22. Red Hat lists fixing advisory RHSA-2026:59153 with package automation-controller-0:4.7.16-1.el9ap, ansible-automation-platform-26/controller-rhel9:1787244009, automation-controller-0:4.6.32-1.el8ap, ansible-automation-platform-27/controller-rhel9:1787220257. Affected products named by the advisory: Red Hat Ansible Automation Platform 2.5 for RHEL 8; Red Hat Ansible Automation Platform 2.5 for RHEL 9; Red Hat Ansible Automation Platform 2.6 for RHEL 9; Red Hat Ansible Automation Platform 2.7.
High [CVE-2026-78367] rpmbuild getTarSpec crafted tar member name → macro injection
rpmbuild getTarSpec() crafted tar member name → macro injection. Red Hat rates this moderate (CVSS 7). Weakness: CWE-94. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; and 3 more. Affected products named by the advisory: Red Hat Enterprise Linux 9; Red Hat Hardened Images; Red Hat package: rpm.
High [CVE-2026-78376] use-after-free of JSCValue function parameters
use-after-free of JSCValue function parameters. Red Hat rates this important (CVSS 8.8). Weakness: CWE-416. Affected products named by the advisory: Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; and 3 more. Affected products named by the advisory: Red Hat package: webkitgtk3; Red Hat package: webkitgtk4; Red Hat package: webkit2gtk3.
High [CVE-2026-76848] Information disclosure via SQL injection in SelectQueryBuilder.distinctOn
Information disclosure via SQL injection in SelectQueryBuilder.distinctOn. Red Hat rates this important (CVSS 7.5). Weakness: CWE-89. Affected products named by the advisory: Red Hat Developer Hub; Self-service automation portal 2.
High [CVE-2026-76844] Information Disclosure via Path Traversal
Information Disclosure via Path Traversal. Red Hat rates this important (CVSS 8.6). Weakness: CWE-22. Affected products named by the advisory: Gatekeeper 3; Migration Toolkit for Containers; Node HealthCheck Operator; OpenShift Lightspeed; and 26 more. Affected products named by the advisory: OpenShift Pipelines; OpenShift Service Mesh 3; Red Hat 3scale API Management Platform 2; Red Hat AMQ Broker 7; and 22 more.
High [CVE-2026-10582] Server-Side Request Forgery (SSRF) leading to information disclosure.
Server-Side Request Forgery (SSRF) leading to information disclosure. Red Hat rates this important (CVSS 7.4). Weakness: CWE-918. Affected products named by the advisory: Red Hat Hardened Images; Red Hat OpenShift GitOps; Red Hat OpenStack Platform 18.0.
High [CVE-2026-76172] URI parsing flaw enables server-side request forgery and redirects
URI parsing flaw enables server-side request forgery and redirects. Red Hat rates this important (CVSS 7.5). Weakness: CWE-76. Affected products named by the advisory: Migration Toolkit for Applications 8; Migration Toolkit for Containers; Multicluster Engine for Kubernetes; Network Observability Operator; and 29 more. Affected products named by the advisory: OpenShift Lightspeed; OpenShift Pipelines; OpenShift Serverless; Red Hat Advanced Cluster Management for Kubernetes 2; and 25 more.
High [CVE-2026-75975] Server-side request forgery via malformed IPv6 normalization
Server-side request forgery via malformed IPv6 normalization. Red Hat rates this important (CVSS 7.5). Weakness: CWE-918. Affected products named by the advisory: Migration Toolkit for Applications 8; Migration Toolkit for Containers; Multicluster Engine for Kubernetes; Network Observability Operator; and 29 more. Affected products named by the advisory: OpenShift Lightspeed; OpenShift Pipelines; OpenShift Serverless; Red Hat Advanced Cluster Management for Kubernetes 2; and 25 more.
High [CVE-2026-75899] Server-Side Request Forgery via repeated hostname percent-decoding
Server-Side Request Forgery via repeated hostname percent-decoding. Red Hat rates this important (CVSS 7.5). Weakness: CWE-140. Affected products named by the advisory: Migration Toolkit for Applications 8; Migration Toolkit for Containers; Multicluster Engine for Kubernetes; Network Observability Operator; and 29 more. Affected products named by the advisory: OpenShift Lightspeed; OpenShift Pipelines; OpenShift Serverless; Red Hat Advanced Cluster Management for Kubernetes 2; and 25 more.