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

Rack has Possible Information Disclosure Vulnerability

rack · rack

Official source article: GitHub GHSA-R657-RXJC-J557 ↗. Check the applicable product and release in the original source.

5.8MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 42 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 severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • 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.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs rack rack 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: As exposure requiresRemediation target: Within 365 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 42 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
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 · sourceruby-rackVendor fix publishedDebian records a fixed source-package version for this release.3.1.18-1~deb13u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceruby-rackVendor fix publishedDebian records a fixed source-package version for this release.2.2.20-0+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceruby-rackVendor fix publishedDebian records a fixed source-package version for this release.3.1.18-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceruby-rackVendor fix publishedDebian records a fixed source-package version for this release.3.1.18-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveruby-rackVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2.2.7-1ubuntu0.5Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 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
RubyGemsrackECOSYSTEM: introduced 0; fixed 2.2.202.2.20OSV record ↗aggregator derived · 10 Sep 2026
RubyGemsrackECOSYSTEM: introduced 3.0; fixed 3.1.183.1.18OSV record ↗aggregator derived · 10 Sep 2026
RubyGemsrackECOSYSTEM: introduced 3.2; fixed 3.2.33.2.3OSV record ↗aggregator derived · 10 Sep 2026
rubygemsrack< 2.2.202.2.20GitHub advisory ↗upstream repository advisory · 13 Oct 2025
rubygemsrack>= 3.0, < 3.1.183.1.18GitHub advisory ↗upstream repository advisory · 13 Oct 2025
rubygemsrack>= 3.2, < 3.2.33.2.3GitHub advisory ↗upstream repository advisory · 13 Oct 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-61780 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityrubygem-rack: Improper handling of headers in `Rack::Sendfile` may allow proxy bypass
42 known affected

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

  • openshift-service-mesh/grafana-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-cni-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-must-gather-rhel9 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-operator-bundle as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-rhel8-operator as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/pilot-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/proxyv2-rhel9 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/ratelimit-rhel8 as a component of OpenShift Service Mesh 2
  • 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/zync-rhel9 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp21/zync as a component of Red Hat 3scale API Management Platform 2
Summary
A potential information disclosure vulnerability has been identified in the RubyGem Rack affecting Rack::Sendfile when used behind a proxy that supports x-sendfile headers (e.g., Nginx). When processing untrusted x-sendfile-type or x-accel-mapping headers, the middleware could misinterpret them as proxy directives, causing the proxy to make unintended internal requests. An attacker could exploit this by sending crafted headers and requesting paths that trigger proxy-based acceleration, potentially accessing internal application endpoints that are normally protected. The issue does not allow arbitrary file reads, code execution, or denial of service.
Remediation
No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.
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-33749

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 42 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

Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.

What

Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Exposure of Sensitive Information to an Unauthorized Actor → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

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

Common Vulnerability Scoring System 3.1: 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.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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.
NetworkUnauthenticatedCWE-200
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20251015Security Bulletin 15 Oct 2025

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

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

d?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-61770 https://www.cve.org/CVERecord?id=CVE-2025-61770 Référence CVE CVE-2025-61771 https://www.cve.org/CVERecord?id=CVE-2025-61771 Référence CVE CVE-2025-61772 https://www.cve.org/CVERecord?id=CVE-2025-61772 Référence CVE CVE-2025-61780 https://www.cve.org/CVERecord?id=CVE-2025-61780 Référence CVE CVE-2025-61795 https://www.cve.org/CVERecord?id=CVE-2025-61795 Référence CVE CVE-2025-61919 https://www.cve.org/CVERecord?id=CVE-2025-61919 Référence CVE CVE-2025-61984 https://www.cve.org/CVERecord?id=CVE-2025-61984 Référence CVE CVE-2025-61985 https://www.cve.org/CVERecord?id=CVE-2025-61985 Référence CVE CVE-2025-62525 https://www.cve.org/CVERecord?id=CVE-2025-62525 Référence CVE CVE-2025-62526 https://www.cve.org/CVERecord?id=CVE-2025-62526 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-61723 Référence CVE CVE-2025-61724 https://www.cve.org/CVERecord?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-61727 https://www.cve.org/CVERecord?id=CVE-2025-61727 Référence CVE CVE-2025-61729 https://www.cve.org/CVERecord?id=CVE-2025-61729 Référence CVE CVE-2025-61748 https://www.cve.org/CVERecord?id=CVE-2025-61748 Référence CVE CVE-2025-61770 https://www.cve.org/CVERecord?id=CVE-2025-61770 Référence CVE CVE-2025-61771 https://www.cve.org/CVERecord?id=CVE-2025-61771 Référence CVE CVE-2025-61772 https://www.cve.org/CVERecord?id=CVE-2025-61772 Référence CVE CVE-2025-61780 https://www.cve.org/CVERecord?id=CVE-2025-61780 Référence CVE CVE-2025-61795 https://www.cve.org/CVERecord?id=CVE-2025-61795 Référence CVE CVE-2025-61919 https://www.cve.org/CVERecord?id=CVE-2025-61919 Référence CVE CVE-2025-64329 https://www.cve.org/CVERecord?id=CVE-2025-64329 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 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-2025-66031 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Gestion détaillée du document le 19 décembre 2025 Version initia

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

/CVERecord?id=CVE-2025-6051 Référence CVE CVE-2025-6052 https://www.cve.org/CVERecord?id=CVE-2025-6052 Référence CVE CVE-2025-6069 https://www.cve.org/CVERecord?id=CVE-2025-6069 Référence CVE CVE-2025-6141 https://www.cve.org/CVERecord?id=CVE-2025-6141 Référence CVE CVE-2025-6170 https://www.cve.org/CVERecord?id=CVE-2025-6170 Référence CVE CVE-2025-61748 https://www.cve.org/CVERecord?id=CVE-2025-61748 Référence CVE CVE-2025-61770 https://www.cve.org/CVERecord?id=CVE-2025-61770 Référence CVE CVE-2025-61771 https://www.cve.org/CVERecord?id=CVE-2025-61771 Référence CVE CVE-2025-61772 https://www.cve.org/CVERecord?id=CVE-2025-61772 Référence CVE CVE-2025-61780 https://www.cve.org/CVERecord?id=CVE-2025-61780 Référence CVE CVE-2025-61795 https://www.cve.org/CVERecord?id=CVE-2025-61795 Référence CVE CVE-2025-61919 https://www.cve.org/CVERecord?id=CVE-2025-61919 Référence CVE CVE-2025-61921 https://www.cve.org/CVERecord?id=CVE-2025-61921 Référence CVE CVE-2025-61984 https://www.cve.org/CVERecord?id=CVE-2025-61984 Référence CVE CVE-2025-61985 https://www.cve.org/CVERecord?id=CVE-2025-61985 Référence CVE CVE-2025-62171 https://www.cve.org/CVERecord?id=CVE-2025-62171 Référence CVE CVE-2025-62813 https://www.cve.org/CVERecord?id=CVE-2025-62813 Référence CVE CVE-2025-6297 https://www.cve.org/CVERecord?id=C

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

ord?id=CVE-2025-58767 Référence CVE CVE-2025-59425 https://www.cve.org/CVERecord?id=CVE-2025-59425 Référence CVE CVE-2025-59830 https://www.cve.org/CVERecord?id=CVE-2025-59830 Référence CVE CVE-2025-6069 https://www.cve.org/CVERecord?id=CVE-2025-6069 Référence CVE CVE-2025-61620 https://www.cve.org/CVERecord?id=CVE-2025-61620 Référence CVE CVE-2025-61748 https://www.cve.org/CVERecord?id=CVE-2025-61748 Référence CVE CVE-2025-61770 https://www.cve.org/CVERecord?id=CVE-2025-61770 Référence CVE CVE-2025-61771 https://www.cve.org/CVERecord?id=CVE-2025-61771 Référence CVE CVE-2025-61772 https://www.cve.org/CVERecord?id=CVE-2025-61772 Référence CVE CVE-2025-61780 https://www.cve.org/CVERecord?id=CVE-2025-61780 Référence CVE CVE-2025-61795 https://www.cve.org/CVERecord?id=CVE-2025-61795 Référence CVE CVE-2025-61919 https://www.cve.org/CVERecord?id=CVE-2025-61919 Référence CVE CVE-2025-61921 https://www.cve.org/CVERecord?id=CVE-2025-61921 Référence CVE CVE-2025-6242 https://www.cve.org/CVERecord?id=CVE-2025-6242 Référence CVE CVE-2025-8194 https://www.cve.org/CVERecord?id=CVE-2025-8194 Référence CVE CVE-2025-8291 https://www.cve.org/CVERecord?id=CVE-2025-8291 Référence CVE CVE-2025-8713 https://www.cve.org/CVERecord?id=CVE-2025-8713 Référence CVE CVE-2025-8714 https://www.cve.org/CVERecord?id=CVE-2025-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014434MIYAGAWA (Tatsuhiko Miyagawa)のPlack::Middleware::Xsendfileにおける複数の脆弱性

Plack::Middleware::XSendfileのPerl用バージョン1.0053以前には、クライアントが制御するパス書き換えを許可する脆弱性が存在します。Plack::Middleware::XSendfileは、ミドルウェアのコンストラクタやPlack環境で適切に考慮されていない場合、クライアントがX-Sendfile-Typeヘッダーを介してsendfileタイプのバリエーション設定を行える状態となっています。悪意のあるクライアントは、nginxリバースプロキシの背後で動作するサービスに対してX-Sendfile-Typeヘッダーを"X-Accel-Redirect"に設定し、その後X-Accel-Mappingを設定してサーバー上の任意のファイルにパスをマッピングすることが可能です。バージョン1.0053以降、Plack::Middleware::XSendfileは非推奨となり、今後のPlackのリリースから削除される予定です。これはRack::Sendfileの類似の問題に関連していますが、Plack::Middleware::XSendfileにはいくつかの軽減策が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-018122Ruby 用 Rack における情報漏えいに関する脆弱性

Ruby 用 Rack には、情報漏えいに関する脆弱性、フィルタリングの回避に関する脆弱性、動的に操作されるコードリソースの不適切な制御に関する脆弱性が存在します。

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
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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 mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.
04

Evidence and provenance

Published 10 Oct 2025 · Last source change 10 Oct 2025, 20:35 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVE recordCVE.org · 5.1
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-33749
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-33749↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-R657-RXJC-J557↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-61780 · cve.blacktree.nl