BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-6176High confidence

Brotli decompression bomb DoS in scrapy/scrapy

scrapy · scrapy/scrapy

7.5HighCVSS 3.0
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 31 Oct 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.55% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs scrapy scrapy/scrapy and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepython-scrapyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython-scrapyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython-scrapyVendor fix publishedDebian records a fixed source-package version for this release.2.13.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython-scrapyVendor fix publishedDebian records a fixed source-package version for this release.2.13.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appspython-scrapyUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIbrotliECOSYSTEM: introduced 0; fixed 1.2.01.2.0OSV record ↗aggregator derived · 10 Sep 2026
PyPIscrapyECOSYSTEM: introduced 0; fixed 2.13.42.13.4OSV record ↗aggregator derived · 10 Sep 2026
pipScrapy<= 2.13.32.13.4GitHub advisory ↗github reviewed aggregator · 17 Nov 2025
pipbrotli<= 1.1.01.2.0GitHub advisory ↗github reviewed aggregator · 17 Nov 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-6176 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityScrapy: python-scrapy: brotli: Python brotli decompression bomb DoS
4 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ansible-automation-platform-tech-preview/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • python3x-brotli.src as a component of Red Hat Ansible Automation Platform 2
  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
  • satellite:el8/python-brotli.src as a component of Red Hat Satellite 6
Summary
Scrapy are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.
Remediation
For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is podman pull quay.io/openshift-release-dev/ocp-release@sha256:07275faf221c556cca2a816cb48a87bdc25a44ff41f91bb88a232c15bc09165e All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-37237

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Scrapy versions up to 2.13.2 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.

What

Scrapy versions up to 2.13.2 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Scrapy versions up to 2.13.2 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Uncontrolled Resource Consumption → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-400Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0783IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2026-0008Red Hat Enterprise Linux: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux bezüglich der Komponenten "tar" und "Scrapy" ausnutzen, um Dateien zu manipulieren, und um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251105Security Bulletin 05 Nov 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 05 Nov 2025, published on 5 November 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-22870 Référence CVE CVE-2025-40252 https://www.cve.org/CVERecord?id=CVE-2025-40252 Référence CVE CVE-2025-41248 https://www.cve.org/CVERecord?id=CVE-2025-41248 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-53643 https://www.cve.org/CVERecord?id=CVE-2025-53643 Référence CVE CVE-2025-58754 https://www.cve.org/CVERecord?id=CVE-2025-58754 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-59472 https://www.cve.org/CVERecord?id=CVE-2025-59472 Référence CVE CVE-2025-6176 https://www.cve.org/CVERecord?id=CVE-2025-6176 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-6545 https://www.cve.org/CVERecord?id=CVE-2025-6545 Référence CVE CVE-2025-6547 https://www.cve.org/CVERecord?id=CVE-2025-6547 Référence CVE CVE-2025-65945 https://www.cve.org/CVERecord?id=CVE-2025-65945 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0327Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2025-5372 Référence CVE CVE-2025-53905 https://www.cve.org/CVERecord?id=CVE-2025-53905 Référence CVE CVE-2025-53906 https://www.cve.org/CVERecord?id=CVE-2025-53906 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-57350 https://www.cve.org/CVERecord?id=CVE-2025-57350 Référence CVE CVE-2025-57352 https://www.cve.org/CVERecord?id=CVE-2025-57352 Référence CVE CVE-2025-57752 https://www.cve.org/CVERecord?id=CVE-2025-57752 Référence CVE CVE-2025-58457 https://www.cve.org/CVERecord?id=CVE-2025-58457 Référence CVE CVE-2025-59250 https://www.cve.org/CVERecord?id=CVE-2025-59250 Référence CVE CVE-2025-6176 https://www.cve.org/CVERecord?id=CVE-2025-6176 Référence CVE CVE-2025-62727 https://www.cve.org/CVERecord?id=CVE-2025-62727 Référence CVE CVE-2025-64775 https://www.cve.org/CVERecord?id=CVE-2025-64775 Référence CVE CVE-2025-6545 https://www.cve.org/CVERecord?id=CVE-2025-6545 Référence CVE CVE-2025-6547 https://www.cve.org/CVERecord?id=CVE-2025-6547 Référence CVE CVE-2025-66418 https://www.cve.org/CVERecord?id=CVE-2025-66418 Référence CVE CVE-2025-66453 https://www.cve.org/CVERecord?id=CVE-2025-66453 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-66675 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-61724 Référence CVE CVE-2025-61725 https://www.cve.org/CVERecord?id=CVE-2025-61725 Référence CVE CVE-2025-61726 https://www.cve.org/CVERecord?id=CVE-2025-61726 Référence CVE CVE-2025-61727 https://www.cve.org/CVERecord?id=CVE-2025-61727 Référence CVE CVE-2025-61728 https://www.cve.org/CVERecord?id=CVE-2025-61728 Référence CVE CVE-2025-61729 https://www.cve.org/CVERecord?id=CVE-2025-61729 Référence CVE CVE-2025-61730 https://www.cve.org/CVERecord?id=CVE-2025-61730 Référence CVE CVE-2025-61731 https://www.cve.org/CVERecord?id=CVE-2025-61731 Référence CVE CVE-2025-61732 https://www.cve.org/CVERecord?id=CVE-2025-61732 Référence CVE CVE-2025-6176 https://www.cve.org/CVERecord?id=CVE-2025-6176 Référence CVE CVE-2025-62408 https://www.cve.org/CVERecord?id=CVE-2025-62408 Référence CVE CVE-2025-62727 https://www.cve.org/CVERecord?id=CVE-2025-62727 Référence CVE CVE-2025-6395 https://www.cve.org/CVERecord?id=CVE-2025-6395 Référence CVE CVE-2025-64505 https://www.cve.org/CVERecord?id=CVE-2025-64505 Référence CVE CVE-2025-64506 https://www.cve.org/CVERecord?id=CVE-2025-64506 Référence CVE CVE-2025-64702 https://www.cve.org/CVERecord?id=CVE-2025-64702 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64720 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 31 Oct 2025 · Last source change 31 Oct 2025, 16:21 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-37237
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    unspecified ≤ latest · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    unspecified ≤ latest · Fixed: For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is podman pull quay.io/openshift-release-dev/ocp-release@sha256:07275faf221c556cca2a816cb48a87bdc25a44ff41f91bb88a232c15bc09165e All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor.
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    ansible-automation-platform-tech-preview/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2; python3x-brotli.src as a component of Red Hat Ansible Automation Platform 2; satellite:el8/python-brotli.src as a component of Red Hat Satellite 6 · Fixed: rhcos-x86_64-412.86.202603041314-0 as a component of Red Hat OpenShift Container Platform 4.12; python-brotli-0:1.2.0-0.1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8; python-brotli-debugsource-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; python3.11-brotli-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; python3.11-brotli-debuginfo-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; rhcos-x86_64-413.92.202602240113-0 as a component of Red Hat OpenShift Container Platform 4.13; rhcos-aarch64-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-ppc64le-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-s390x-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-x86_64-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-aarch64-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-ppc64le-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-s390x-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-x86_64-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-aarch64-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-ppc64le-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-s390x-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-x86_64-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-aarch64-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-ppc64le-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-s390x-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-x86_64-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-aarch64-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-ppc64le-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-s390x-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-x86_64-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-aarch64-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-ppc64le-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-s390x-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-x86_64-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; and 703 more
    After
    ansible-automation-platform-tech-preview/automation-dashboard-rhel9 as a component of Red Hat Ansible Automation Platform 2; python3x-brotli.src as a component of Red Hat Ansible Automation Platform 2; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4; satellite:el8/python-brotli.src as a component of Red Hat Satellite 6 · Fixed: rhcos-x86_64-412.86.202603041314-0 as a component of Red Hat OpenShift Container Platform 4.12; python-brotli-0:1.2.0-0.1.el8pc.src as a component of Red Hat Satellite 6.16 for RHEL 8; python-brotli-debugsource-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; python3.11-brotli-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; python3.11-brotli-debuginfo-0:1.2.0-0.1.el8pc.x86_64 as a component of Red Hat Satellite 6.16 for RHEL 8; rhcos-x86_64-413.92.202602240113-0 as a component of Red Hat OpenShift Container Platform 4.13; rhcos-aarch64-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-ppc64le-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-s390x-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-x86_64-414.92.202602171627-0 as a component of Red Hat OpenShift Container Platform 4.14; rhcos-aarch64-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-ppc64le-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-s390x-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-x86_64-415.92.202603101737-0 as a component of Red Hat OpenShift Container Platform 4.15; rhcos-aarch64-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-ppc64le-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-s390x-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-x86_64-416.94.202603112010-0 as a component of Red Hat OpenShift Container Platform 4.16; rhcos-aarch64-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-ppc64le-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-s390x-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-x86_64-417.94.202602251654-0 as a component of Red Hat OpenShift Container Platform 4.17; rhcos-aarch64-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-ppc64le-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-s390x-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-x86_64-418.94.202602172219-0 as a component of Red Hat OpenShift Container Platform 4.18; rhcos-aarch64-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-ppc64le-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-s390x-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; rhcos-x86_64-4.19.9.6.202602252137-0 as a component of Red Hat OpenShift Container Platform 4.19; and 703 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-6176 · cve.blacktree.nl