Complete feed
Recently updated
Advisories the vendor has revised
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.
Medium [CVE-2026-19499] Buffer Overflow in strfmon right-justification padding
Buffer Overflow in strfmon right-justification padding. Red Hat rates this moderate (CVSS 6.8). Weakness: CWE-787. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Hardened Images; Red Hat package: glibc.
Medium [CVE-2026-78322] stack buffer overflow in parse_progress_line for 7z and RAR handlers
stack buffer overflow in parse_progress_line for 7z and RAR handlers. Red Hat rates this moderate (CVSS 6.5). Weakness: CWE-120. Affected products named by the advisory: Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat package: file-roller.
Medium [CVE-2026-19542] Fix out-of-bounds array write in tdelete
Fix out-of-bounds array write in tdelete. Red Hat rates this moderate (CVSS 4.2). Weakness: CWE-787. Red Hat lists fixing advisory RHSA-2026:59721 with package glibc-main-2.43-8.2.hum1. Affected products named by the advisory: Red Hat Hardened Images; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; Red Hat package: glibc.
Medium [CVE-2026-59183] Integer Overflow Vulnerability Leading to Application Crash
Integer Overflow Vulnerability Leading to Application Crash. Red Hat rates this moderate (CVSS 5.5). Weakness: CWE-125. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; Red Hat package: openexr.
Medium [CVE-2026-55373] Denial of Service via infinite loop in sample count processing.
Denial of Service via infinite loop in sample count processing. Red Hat rates this moderate (CVSS 6.2). Weakness: CWE-835. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat package: openexr.
Medium [CVE-2026-55371] Denial of Service via NULL pointer dereference in exr_attr_set_bytes
Denial of Service via NULL pointer dereference in exr_attr_set_bytes(). Red Hat rates this moderate (CVSS 5.5). Weakness: CWE-476.
Medium [CVE-2026-55059] Heap out-of-bounds write leads to denial of service
Heap out-of-bounds write leads to denial of service. Red Hat rates this moderate (CVSS 5.5). Weakness: CWE-124. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat package: openexr.
Medium [CVE-2026-54920] Denial of Service via crafted HTJ2K-compressed EXR file
Denial of Service via crafted HTJ2K-compressed EXR file. Red Hat rates this moderate (CVSS 6.5). Weakness: CWE-617.
Medium [CVE-2026-63073] untrusted sender DN used as format string in CMP response validation
untrusted sender DN used as format string in CMP response validation. Red Hat rates this low (CVSS 5.9). Weakness: CWE-134. Red Hat lists fixing advisory RHSA-2026:59641 with package openssl3-main-3.5.8-0.1.hum1, openssl-main-3.5.8-0.1.hum1. Affected products named by the advisory: Red Hat Hardened Images; Red Hat Developer Hub; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9; and 6 more. Affected products named by the advisory: Red Hat JBoss Core Services; Red Hat JBoss Web Server 6; Red Hat JBoss Web Server 7; Red Hat OpenShift Container Platform 4; and 2 more.
Medium [CVE-2026-58070] Vulnerability Resolved in Veeam Backup & Replication 13.1
Vulnerability Resolved in Veeam Backup & Replication 13.1 KB ID: 4902 Product: Published: 2026-08-25 Last Modified: Veeam Software Security Commitment Veeam® is committed to ensuring its products protect customers from potential risks. As part of that commitment, we operate a Vulnerability Disclosure Program (VDP) for all Veeam products and perform extensive internal code audits. When a vulnerability is identified, our team promptly develops a patch to address and mitigate the risk. In line with our dedication to transparency, we publicly disclose the vulnerability and provide detailed mitigation information. This approach ensures that all potentially affected customers can quickly implement the necessary measures to safeguard their systems. It’s important to note that once a vulnerability and its associated patch are disclosed, attackers will likely attempt to reverse-engineer the patch to exploit unpatched deployments of Veeam software. This reality underscores the critical importance of ensuring that all customers use the latest versions of our software and install all updates and patches without delay. Issue Details A vulnerability that causes guest OS credentials used for Application Aware processing to be recorded in cleartext in logs on the guest machine. Severity: Medium CVSS v4.0 Score: 6.8CVSS: AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Low [CVE-2025-71346] Heap buffer under-read in XML Schema validation
Heap buffer under-read in XML Schema validation. Red Hat rates this low (CVSS 2.9). Weakness: CWE-125. Affected products named by the advisory: Red Hat 3scale API Management Platform 2; Red Hat Satellite 6.
Advisory [CVE-2021-35971 +44] List of Security Fixes and Improvements in Veeam Backup & Replication
List of Security Fixes and Improvements in Veeam Backup & Replication KB ID: 3103 Product: Published: 2020-03-02 Last Modified: 2026-08-21 Purpose 13.1.0.411 - System. Security. Cryptography. Xml upgraded to version 10.0.7 - Microsoft. AspNetCore. DataProtection upgraded to version 10.0.7 - CoreWCF.Primitives upgraded to version 1.8.1 - MailKit upgraded to version 4.17.0 - MimeKit upgraded to version 4.17.0 - OpenTelemetry upgraded to version 1.15.3 - SQLite upgraded to version 3.53.2 - @angular/core upgraded to version 21.2.17 - OpenSSL upgraded to version 3.5.7 - curl upgraded to version 8.21.0 - zlib upgraded to version 1.3.2 - libarchive upgraded to version 3.8.5 13.0.3.63 - dompurify upgraded to version 3.4.12 13.0.2.29 - uuid upgraded to version 14.0.0 - Snappier upgraded to version 1.3.1 - picomatch upgraded to version 2.3.2 - Microsoft. Kiota. Abstractions upgraded to version 1.22.0 - lodash upgraded to version 4.18.1 - AutoMapper replaced with MagicMapper 14.0.1 13.0.1.2067 13.0.1.1071 - CVE-2025-55125 vulnerability was fixed. 13.0.1.180 - Microsoft. IdentityModel. JsonWebTokens upgraded to version 8.12.0 13.0.0.4967 - Communication protocol was switched to gRPC - Libxml2 upgraded to version 2.13.8 - Newtonsoft. Json upgraded to version 13.0.1 - RestSharp upgraded to version 112.1.0 - Microsoft. Extensions. Caching. Memory upgraded to version 8.0.1
Advisory [CVE-2022-26503 +5] List of Security Fixes and Improvements in Veeam Agent for Microsoft Windows
List of Security Fixes and Improvements in Veeam Agent for Microsoft Windows KB ID: 3108 Product: Published: 2020-03-02 Last Modified: 2026-08-25 Purpose 13.1.0.544 - MessagePack upgraded to version 2.5.302 - OpenSSL upgraded to version 3.5.7 13.0.4.1341 - SQLite upgraded to version 3.53.2 13.0.3.1220 - Microsoft. Kiota. Abstractions upgraded to version 1.22.0 13.0.1.120 13.0.0.835 - Communication protocol was switched to gRPC - System. IdentityModel. Tokens. Jwt upgraded to version 8.0.2 6.3.2.1302 - CVE-2025-48982 vulnerability was fixed. 6.3.2.1205 6.3.0.177 - Vulnerability ( CVE-2024-45207 ) in Veeam Agent for Microsoft Windows was fixed. 6.1.2.134 6.1.0.349 - OpenSSL library updated to 1.0.2zi. - LZ4 library updated to 1.9.4. - Stronger backup encryption. - (See pg. 7 of Veeam Backup & Replication 12.1 What's New PDF ) 6.0.2.1090 6.0.0.960 - Added support for networks with NTLM authentication disabled ( Kerberos-only authentication ). - Audit capabilities were improved. - zlib has been updated to version 1.2.13. 5.0.3.5029 - liblz4 was updated to v1.9.4. - zlib was updated to v1.2.13. - PuTTY was updated to 0.80. 5.0.3.4708 5.0.0.4301 4.0.2.2208 4.0.0.1811 - A custom security descriptor was provided for the driver's control device (vulnerability reported by Mile Karry).
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-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.