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

Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)

authlib · authlib

Official source article: GitHub GHSA-9GGR-2464-2J32 ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 3 Nov 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.26% 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 authlib authlib 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.

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 · sourcepython-authlibVendor fix publishedDebian records a fixed source-package version for this release.1.6.0-1+deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepython-authlibVendor fix publishedDebian records a fixed source-package version for this release.1.2.0-1+deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepython-authlibVendor fix publishedDebian records a fixed source-package version for this release.1.6.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepython-authlibVendor fix publishedDebian records a fixed source-package version for this release.1.6.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appspython-authlibVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.3.0-1ubuntu0.1~esm1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 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
PyPIauthlibECOSYSTEM: introduced 0; fixed 1.6.41.6.4OSV record ↗aggregator derived · 10 Sep 2026
pipauthlib< 1.6.41.6.4GitHub advisory ↗upstream repository advisory · 3 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-59420 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityauthlib: Authlib RFC violation
31 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • registry.redhat.io/quay/quay-rhel8@sha256:2b5f83bbade40b04a7975788743afdb8cec5f72ad8e5eea4c75d5840ce44ef3f_s390x as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:7b77b205b95f99383f12e571b391a35ea8f85dfd23f2d4fd67045bbece1ee66e_amd64 as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:b638f53267de38576f1875ee3379114ba3c2089d8b26901c4a960ec82d35a0b6_ppc64le as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:cb10c70bfb9d8dc3f7bc75506901cd84af0cd11e21883f78d651838eaa83c16c_amd64 as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:d0ad53575ddce599c11e959d3590300ab325633951003db4ef2d82a133c8ef19_arm64 as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:f5047f7dea7825a5d0ad7323f433af0ce17fea83d1d3861372edd682584bb30e_ppc64le as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:f8c677a9fc5a608bc6c1848db7e3ff906ea93cb9cbc92af3d574c3158b2af668_s390x as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:fe48d48bb338329da213a0a21d2ac706b4b731593f154d554bfd420ad21a2912_arm64 as a component of Red Hat Quay 3.10
  • registry.redhat.io/quay/quay-rhel8@sha256:30152d31da209c034ec39b52a32063437097eec9a4fac2eaf4a4110fea97cb70_arm64 as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-rhel8@sha256:38f094f62eed92d88eae0e7a9be410ef908bd0194b30240d49087ae76250e0ee_ppc64le as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-rhel8@sha256:4d0a86e557e93eb8e7d70d538f181c2d33176b3537fb8d9e3a1e76a16ee2eed5_s390x as a component of Red Hat Quay 3.12
  • registry.redhat.io/quay/quay-rhel8@sha256:a40309477f7286b6c00381012eec8d3ececb557a4b8db38e5b4ea7f321a17c79_amd64 as a component of Red Hat Quay 3.12
Summary
Authlib’s JWS verification accepts tokens that declare unknown critical header parameters (crit), violating RFC 7515 “must‑understand” semantics. An attacker can craft a signed token with a critical header (for example, bork or cnf) that strict verifiers reject but Authlib accepts. In mixed‑language fleets, this enables split‑brain verification and can lead to policy bypass, replay, or privilege escalation.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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-30790

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 actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.4, Authlib’s JWS verification accepts tokens that declare unknown critical header parameters (crit), violating RFC 7515 “must‑understand” semantics. An attacker can craft a signed token with a critical header (for example, bork or cnf) that strict verifiers reject but Authlib accepts. In mixed‑language fleets, this enables split‑brain verification and can lead to policy bypass, replay, or privilege escalation. This issue has been patched in version 1.6.4.

What

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.4, Authlib’s JWS verification accepts tokens that declare unknown critical header parameters (crit), violating RFC 7515 “must‑understand” semantics. An attacker can craft a signed token with a critical header (for example, bork or cnf) that strict verifiers reject but Authlib accepts. In mixed‑language fleets, this enables split‑brain verification and can lead to policy bypass, replay, or privilege escalation. This issue has been patched in version 1.6.4.

Why

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

What

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.4, Authlib’s JWS verification accepts tokens that declare unknown critical header parameters (crit), violating RFC 7515 “must‑understand” semantics. An attacker can craft a signed token with a critical header (for example, bork or cnf) that strict verifiers reject but Authlib accepts. In mixed‑language fleets, this enables split‑brain verification and can lead to policy bypass, replay, or privilege escalation. This issue has been patched in version 1.6.4.

Why

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

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

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Insufficient Verification of Data Authenticity → gain additional privileges
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-345 ↗

CWE-345: Insufficient Verification of Data Authenticity. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

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:U/C:N/I:H/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.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedPrivilege escalationCWE-345Public exploit reference
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-20250924Security Bulletin 24 Sep 2025

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

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-016332authlib におけるデータの信頼性についての不十分な検証に関する脆弱性

authlib には、データの信頼性についての不十分な検証に関する脆弱性、不正な認証に関する脆弱性が存在します。

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.
Patch available
Affected
authlib: < 1.6.4
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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 22 Sept 2025 · Last source change 3 Nov 2025, 17:45 UTC · CWE-345 · Insufficient Verification of Data Authenticity

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-30790
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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
    < 1.6.4 · 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.
    After
    < 1.6.4 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: registry.redhat.io/quay/quay-rhel8@sha256:30152d31da209c034ec39b52a32063437097eec9a4fac2eaf4a4110fea97cb70_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:38f094f62eed92d88eae0e7a9be410ef908bd0194b30240d49087ae76250e0ee_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:4d0a86e557e93eb8e7d70d538f181c2d33176b3537fb8d9e3a1e76a16ee2eed5_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:a40309477f7286b6c00381012eec8d3ececb557a4b8db38e5b4ea7f321a17c79_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:0b00334468578780a4e4b34c03260e57aa07ec47b0d4860b17c8ec964eb7634d_arm64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:1d15d8b7f90327a4216efba353d61c94a9438e5a8df3e68da44907816943d0d3_ppc64le as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:28b200a0ba2c8095d93fc95edbdcdf83b2507a7379f2842fc0a1b7cc5fdd839c_s390x as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:3d24fd39236e7f3180ff2cbef7a28e2e30d9609f6ec0538a41ad4a602eabd12e_amd64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:05cc4b4410de27e32897492effb21362d8c1bc8cc56e9408fc9a19f9f3149899_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:225e2bed98b80e753ba2eca6b121a7295b20633b25b8098b7dce66efc2bc1b70_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:51881be0039c3a7df9ad588060955dc3f0ea6eef28a35ebc4fe146e73316e2a4_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:e2a2347a1ed65e94a13fd0330e7922339096d725733071a1f9eb4c413be5eb90_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:08a827d542790820a10a61bacdc8ab7c05a6fdd476f1224ed76f20d65e93673f_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:7bfb851938e312f47598891ba9f0d7b17e6657090e0204d37d5676313b33f134_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:a8daa359ab7a0bc9722b25fb87aa6fd253506632640bfe7f31c9c92868421ecb_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:2b5f83bbade40b04a7975788743afdb8cec5f72ad8e5eea4c75d5840ce44ef3f_s390x as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:7b77b205b95f99383f12e571b391a35ea8f85dfd23f2d4fd67045bbece1ee66e_amd64 as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:b638f53267de38576f1875ee3379114ba3c2089d8b26901c4a960ec82d35a0b6_ppc64le as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:cb10c70bfb9d8dc3f7bc75506901cd84af0cd11e21883f78d651838eaa83c16c_amd64 as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:d0ad53575ddce599c11e959d3590300ab325633951003db4ef2d82a133c8ef19_arm64 as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:f5047f7dea7825a5d0ad7323f433af0ce17fea83d1d3861372edd682584bb30e_ppc64le as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:f8c677a9fc5a608bc6c1848db7e3ff906ea93cb9cbc92af3d574c3158b2af668_s390x as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:fe48d48bb338329da213a0a21d2ac706b4b731593f154d554bfd420ad21a2912_arm64 as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:1cb5d4a87d8bd300edace58d2f3658e1296a23c0d4fed13fd0baa2fdb1da27d8_amd64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:1e95647d265fcc668bb66cc83fff56eb00eb2a7a4c8a7a2d86186bdc68de3ea0_ppc64le as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:2336ad8d4b4874a92c6cfcbc8458b6d26f7f6dde300ca0e159f2b73d7e6839cd_arm64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:55a8de289089989f26365c0011d30310fdc525e8515f7be94956b8c21769edda_s390x as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:628dd4acfe11aef376cc6d75dc7c337c1e487113c2e78e003a3377472b22f488_ppc64le as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:a6813e5bf29916abf84b2d120a30cda07edf06f735c860ee4d0510ed0c59633b_amd64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:c7c6fe7ff2592c0fdf51d6e3b0ce657dffcd131c60c00ce680acd89c5c286cee_s390x as a component of Red Hat Quay 3.9; and 1 more
    After
    Fixed: registry.redhat.io/quay/quay-rhel8@sha256:2b5f83bbade40b04a7975788743afdb8cec5f72ad8e5eea4c75d5840ce44ef3f_s390x as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:7b77b205b95f99383f12e571b391a35ea8f85dfd23f2d4fd67045bbece1ee66e_amd64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:b638f53267de38576f1875ee3379114ba3c2089d8b26901c4a960ec82d35a0b6_ppc64le as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:cb10c70bfb9d8dc3f7bc75506901cd84af0cd11e21883f78d651838eaa83c16c_amd64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:d0ad53575ddce599c11e959d3590300ab325633951003db4ef2d82a133c8ef19_arm64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:f5047f7dea7825a5d0ad7323f433af0ce17fea83d1d3861372edd682584bb30e_ppc64le as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:f8c677a9fc5a608bc6c1848db7e3ff906ea93cb9cbc92af3d574c3158b2af668_s390x as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:fe48d48bb338329da213a0a21d2ac706b4b731593f154d554bfd420ad21a2912_arm64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:30152d31da209c034ec39b52a32063437097eec9a4fac2eaf4a4110fea97cb70_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:38f094f62eed92d88eae0e7a9be410ef908bd0194b30240d49087ae76250e0ee_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:4d0a86e557e93eb8e7d70d538f181c2d33176b3537fb8d9e3a1e76a16ee2eed5_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:a40309477f7286b6c00381012eec8d3ececb557a4b8db38e5b4ea7f321a17c79_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:0b00334468578780a4e4b34c03260e57aa07ec47b0d4860b17c8ec964eb7634d_arm64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:1d15d8b7f90327a4216efba353d61c94a9438e5a8df3e68da44907816943d0d3_ppc64le as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:28b200a0ba2c8095d93fc95edbdcdf83b2507a7379f2842fc0a1b7cc5fdd839c_s390x as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:3d24fd39236e7f3180ff2cbef7a28e2e30d9609f6ec0538a41ad4a602eabd12e_amd64 as a component of Red Hat Quay 3.13; registry.redhat.io/quay/quay-rhel8@sha256:05cc4b4410de27e32897492effb21362d8c1bc8cc56e9408fc9a19f9f3149899_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:225e2bed98b80e753ba2eca6b121a7295b20633b25b8098b7dce66efc2bc1b70_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:51881be0039c3a7df9ad588060955dc3f0ea6eef28a35ebc4fe146e73316e2a4_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:e2a2347a1ed65e94a13fd0330e7922339096d725733071a1f9eb4c413be5eb90_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:08a827d542790820a10a61bacdc8ab7c05a6fdd476f1224ed76f20d65e93673f_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:7bfb851938e312f47598891ba9f0d7b17e6657090e0204d37d5676313b33f134_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:a8daa359ab7a0bc9722b25fb87aa6fd253506632640bfe7f31c9c92868421ecb_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:1cb5d4a87d8bd300edace58d2f3658e1296a23c0d4fed13fd0baa2fdb1da27d8_amd64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:1e95647d265fcc668bb66cc83fff56eb00eb2a7a4c8a7a2d86186bdc68de3ea0_ppc64le as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:2336ad8d4b4874a92c6cfcbc8458b6d26f7f6dde300ca0e159f2b73d7e6839cd_arm64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:55a8de289089989f26365c0011d30310fdc525e8515f7be94956b8c21769edda_s390x as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:628dd4acfe11aef376cc6d75dc7c337c1e487113c2e78e003a3377472b22f488_ppc64le as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:a6813e5bf29916abf84b2d120a30cda07edf06f735c860ee4d0510ed0c59633b_amd64 as a component of Red Hat Quay 3.9; registry.redhat.io/quay/quay-rhel8@sha256:c7c6fe7ff2592c0fdf51d6e3b0ce657dffcd131c60c00ce680acd89c5c286cee_s390x as a component of Red Hat Quay 3.9; and 1 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-30790↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-9GGR-2464-2J32↗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-59420 · cve.blacktree.nl