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

Go JOSE's Parsing Vulnerable to Denial of Service

go-jose · go-jose

Official source article: GitHub GHSA-C6GW-W398-HV78 ↗. Check the applicable product and release in the original source.

6.6MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
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.40% 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 go-jose go-jose 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.

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.

4 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 · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegolang-github-go-jose-go-joseVendor fix publishedDebian records a fixed source-package version for this release.4.0.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-go-jose-go-joseUnder 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 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
Gogithub.com/go-jose/go-joseSEMVER: introduced 0; fixed 3.0.43.0.4OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-jose/go-jose/v3SEMVER: introduced 0; fixed 3.0.43.0.4OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/go-jose/go-jose/v4SEMVER: introduced 0; fixed 4.0.54.0.5OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/go-jose/go-jose< 3.0.43.0.4GitHub advisory ↗upstream repository advisory · 26 Feb 2025
gogithub.com/go-jose/go-jose/v3< 3.0.43.0.4GitHub advisory ↗upstream repository advisory · 26 Feb 2025
gogithub.com/go-jose/go-jose/v4< 4.0.54.0.5GitHub advisory ↗upstream repository advisory · 26 Feb 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.

2 current
CVE-2025-27144 · CSAF 2.0 · revision 100 · interimSUSE Product Security TeamCVE-2025-27144
322 known affected

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

  • buildah as component of SLES-LTSS-TERADATA 15 SP2
  • containerd as component of SLES-LTSS-TERADATA 15 SP2
  • containerized-data-importer as component of SLES-LTSS-TERADATA 15 SP2
  • podman as component of SLES-LTSS-TERADATA 15 SP2
  • containerd as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • containerd-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • buildah as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • containerd as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • containerd-ctr as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • podman as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • podman-cni-config as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-27144 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygo-jose: Go JOSE's Parsing Vulnerable to Denial of Service
24 known affected

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

  • cert-manager-operator-rhel9 as a component of cert-manager Operator for Red Hat OpenShift
  • multicluster-engine/assisted-installer-agent-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-installer-controller-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-installer-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-service-8-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-service-9-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/hypershift-cli-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/hypershift-rhel8-operator as a component of Multicluster Engine for Kubernetes
  • openshift-pipelines-client.src as a component of OpenShift Pipelines
  • openshift-istio-cni-container as a component of OpenShift Service Mesh 3
  • openshift-istio-must-gather-container as a component of OpenShift Service Mesh 3
  • openshift-istio-pilot-container as a component of OpenShift Service Mesh 3
Summary
A flaw was found in GO-JOSE. In affected versions, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code uses strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. This issue could be exploied by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service.
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-4268

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.

What

Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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

Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of `.` characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of `.` characters.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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.
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 → Allocation of Resources Without Limits or Throttling → 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
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

Common Vulnerability Scoring System 4.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.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: 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.
NetworkUnauthenticatedDenial of serviceCWE-770
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0625Red Hat OpenShift Container Platform: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250226Security Bulletin 26 Feb 2025

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

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

d?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3360 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-24294 https://www.cve.org/CVERecord?id=CVE-2025-24294 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-26646 https://www.cve.org/CVERecord?id=CVE-2025-26646 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-30215 https://www.cve.org/CVERecord?id=CVE-2025-30215 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-30761 https://www.cve.org/CVERecord?id=CVE-2025-30761 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-31651 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-24855 Référence CVE CVE-2025-24928 https://www.cve.org/CVERecord?id=CVE-2025-24928 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-25186 https://www.cve.org/CVERecord?id=CVE-2025-25186 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-25724 https://www.cve.org/CVERecord?id=CVE-2025-25724 Référence CVE CVE-2025-26465 https://www.cve.org/CVERecord?id=CVE-2025-26465 Référence CVE CVE-2025-26603 https://www.cve.org/CVERecord?id=CVE-2025-26603 Référence CVE CVE-2025-27113 https://www.cve.org/CVERecord?id=CVE-2025-27113 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-27219 https://www.cve.org/CVERecord?id=CVE-2025-27219 Référence CVE CVE-2025-27220 https://www.cve.org/CVERecord?id=CVE-2025-27220 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-27363 https://www.cve.org/CVERecord?id=CVE-2025-27363 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27587 https://www.cve.org/CVERecord?id=CVE-2025-27587 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0960Multiples vulnérabilités dans VMware Tanzu

ord?id=CVE-2024-53427 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-22866 https://www.cve.org/CVERecord?id=CVE-2025-22866 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-48060 https://www.cve.org/CVERecord?id=CVE-2025-48060 Gestion détaillée du document le 04 novembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À

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

ord?id=CVE-2025-24294 Référence CVE CVE-2025-2476 https://www.cve.org/CVERecord?id=CVE-2025-2476 Référence CVE CVE-2025-24813 https://www.cve.org/CVERecord?id=CVE-2025-24813 Référence CVE CVE-2025-24855 https://www.cve.org/CVERecord?id=CVE-2025-24855 Référence CVE CVE-2025-24928 https://www.cve.org/CVERecord?id=CVE-2025-24928 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-26519 https://www.cve.org/CVERecord?id=CVE-2025-26519 Référence CVE CVE-2025-27113 https://www.cve.org/CVERecord?id=CVE-2025-27113 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27587 https://www.cve.org/CVERecord?id=CVE-2025-27587 Référence CVE CVE-2025-27817 https://www.cve.org/CVERecord?id=CVE-2025-27817 Référence CVE CVE-2025-27818 https://www.cve.org/CVERecord?id=CVE-2025-27818 Référence CVE CVE-2025-2783 https://www.cve.org/CVERecord?id=CVE-2025-2783 Référence CVE CVE-2025-2817 https://www.cve.org/CVERecord?id=CVE-2025-2817 Référence CVE CVE-2025-2857 https://www.cve.org/CVERecord?id=CVE-2

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

ord?id=CVE-2024-42461 Référence CVE CVE-2024-48948 https://www.cve.org/CVERecord?id=CVE-2024-48948 Référence CVE CVE-2024-49766 https://www.cve.org/CVERecord?id=CVE-2024-49766 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-56128 https://www.cve.org/CVERecord?id=CVE-2024-56128 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2025-21502 https://www.cve.org/CVERecord?id=CVE-2025-21502 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-25977 https://www.cve.org/CVERecord?id=CVE-2025-25977 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Gestion détaillée du document le 31 juillet 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2025-22235 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-24928 https://www.cve.org/CVERecord?id=CVE-2025-24928 Référence CVE CVE-2025-25019 https://www.cve.org/CVERecord?id=CVE-2025-25019 Référence CVE CVE-2025-25020 https://www.cve.org/CVERecord?id=CVE-2025-25020 Référence CVE CVE-2025-25021 https://www.cve.org/CVERecord?id=CVE-2025-25021 Référence CVE CVE-2025-25022 https://www.cve.org/CVERecord?id=CVE-2025-25022 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CVE-2025-26791 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27363 https://www.cve.org/CVERecord?id=CVE-2025-27363 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-30691 https://www.cve.org/CVERecord?id=CVE-2025-30691 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-32996 https://www.cve.org/CVERecord?id=CVE-2025-32996 Référence CVE CVE-2025-32997 https://www.cve.org/CVERecord?id=CVE-2025-32997 Gestion détaillée du document le 06 juin 2025 Version initiale

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
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
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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 24 Feb 2025 · Last source change 25 Feb 2025, 14:27 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

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-4268
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
    >= 4.0.0, < 4.0.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 4.0.0, < 4.0.5 · 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. 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
    cert-manager-operator-rhel9 as a component of cert-manager Operator for Red Hat OpenShift; multicluster-engine/assisted-installer-agent-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-installer-controller-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-installer-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-service-8-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-service-9-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-cli-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-rhel8-operator as a component of Multicluster Engine for Kubernetes; openshift-pipelines-client.src as a component of OpenShift Pipelines; openshift-istio-cni-container as a component of OpenShift Service Mesh 3; openshift-istio-must-gather-container as a component of OpenShift Service Mesh 3; openshift-istio-pilot-container as a component of OpenShift Service Mesh 3; openshift-istio-proxyv2-container as a component of OpenShift Service Mesh 3; authorino-container as a component of Red Hat 3scale API Management Platform 2; authorino-container as a component of Red Hat Connectivity Link 1; bootc-image-builder as a component of Red Hat Enterprise Linux 10; cri-o as a component of Red Hat OpenShift Container Platform 4; cri-o.src as a component of Red Hat OpenShift Container Platform 4; openshift-clients as a component of Red Hat OpenShift Container Platform 4; openshift-clients-redistributable as a component of Red Hat OpenShift Container Platform 4; openshift-clients.src as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-cli-artifacts as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-deployer as a component of Red Hat OpenShift Container Platform 4; rosa.src as a component of Red Hat OpenShift on AWS · Fixed: openshift-gitops-1/argo-rollouts-rhel8@sha256:1c3014b6fed55efec858979b8e716025b3c930ce73ce03376d6b344cc799f408_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:c0b31a9043e01767c4305bf53852e4e956a75bbf0d338e9bdd84693d854aadb1_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:cffc1a5602bc8275c83aff3a8397dc812b925494deb8105bad675e1eebc1ce4f_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:f1551e8646b6f845566aa3786194b2cb3392240617ec33a8598e1361a2f7cf6e_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:2959776572015171fe9e674bef16cd27207ad0dd9778597f61c92bd0b68419cb_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:6751efa0700ce5aca7e998b507f2694d36671c800bd3df39c1793fdb79295b01_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:7de02503f35ffa0385273117b00104f7cd13cf62e90236a539b00d0a26914fe5_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:9628abc742fa7d3e4e7f76c42f86f729a12064b31c6fdcd4d56fd12de42c312d_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:2b613ea76cf38f82b81c0f94bc1310f8221ebfae30e11bb3eb9a9322f7de781c_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:9b2b128beada3283376cb1e0daa09f3074e865cd13feff7e5cf4be22b80b73eb_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:adff90e820d35b5f6edb54e8a3e66a1944b3df7949b82b52757542990532a927_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:c828786304a861504124f4adcef108a8ec2fbb1ffe39c6f40cbcd45421d9da63_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:23d6aff07ace832a252e24f8c4f50fa7bb8071195266ca2ee1ecb85d2c8cd040_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:7cf81305f51be21dd5044cf2b5e252c3504a5593b25c79efd14ac4c07b845e0e_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:b7729386eafdea2376dd9b95e2f30904f0a737108fa01643425a26817b2d49e3_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:bd66924e532f909e4efe16a7d02556ce50d3aeb399a1c576365c58e28b217156_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:3763f158afee4709f908f9069cafc53e6e19932a89206e1b1c161b83978c8bf3_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:4f556b4a5eb754b8310db23d78984612ce6fb1537a96cf5bba1ca4d9db24c458_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:5322e7c5c3e6648cbc31aef26c793fe446de59f926c9e420e7bbe69be5b7628c_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:575fe0d90e61cd644293c9775b0b6670b159bf0e004b1514f65473a353ed157e_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-operator-bundle@sha256:9233f5165c36e049c07f6c86bc4a330e8cd5c92fdb9e26364f83156e5079a573_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:1ec8b3afca8969bb43413de847e9e42e863a00e618b2d75585a297f605d4c2cd_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:b5bad8e3002354e708978aa81d8fb12ce244336677dd4b43d05a2e3d28ee21fe_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:c11750919f393a494bd39f5430dd64502fda211e1e58b82b12b25c0aefb01b10_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:f44ea91f40a80ea0ceb8ce162344632fa4ac83a25e40e3e268a04960dd4cef8e_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:02615dcef407b4c180d2136fd2d0179b75a938663530173c3155fc137158b9ef_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:2fdc37ff27fe77bcf1b49b5067cc29250ec8e1073a1e3d747c46471a12a23bd2_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:bab70614afc93dde060a53ae72f677c979851881160f434a7b3a82c208122222_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:bfd4fc073330dff519a73394fd300f304dce3b7d4de1cc741324af08085819e6_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/must-gather-rhel8@sha256:a19ac137261209f8d9a0648179637ea7c2a4e0e605c6f1370de6f74deea62676_arm64 as a component of Red Hat OpenShift GitOps 1.15; and 1000 more
    After
    cert-manager-operator-rhel9 as a component of cert-manager Operator for Red Hat OpenShift; multicluster-engine/assisted-installer-agent-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-installer-controller-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-installer-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-service-8-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/assisted-service-9-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-cli-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-rhel8-operator as a component of Multicluster Engine for Kubernetes; openshift-pipelines-client.src as a component of OpenShift Pipelines; openshift-istio-cni-container as a component of OpenShift Service Mesh 3; openshift-istio-must-gather-container as a component of OpenShift Service Mesh 3; openshift-istio-pilot-container as a component of OpenShift Service Mesh 3; openshift-istio-proxyv2-container as a component of OpenShift Service Mesh 3; authorino-container as a component of Red Hat 3scale API Management Platform 2; authorino-container as a component of Red Hat Connectivity Link 1; bootc-image-builder as a component of Red Hat Enterprise Linux 10; cri-o as a component of Red Hat OpenShift Container Platform 4; cri-o.src as a component of Red Hat OpenShift Container Platform 4; openshift-clients as a component of Red Hat OpenShift Container Platform 4; openshift-clients-redistributable as a component of Red Hat OpenShift Container Platform 4; openshift-clients.src as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-cli-artifacts-rhel9 as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-deployer as a component of Red Hat OpenShift Container Platform 4; rosa.src as a component of Red Hat OpenShift on AWS · Fixed: openshift-gitops-1/argo-rollouts-rhel8@sha256:1c3014b6fed55efec858979b8e716025b3c930ce73ce03376d6b344cc799f408_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:c0b31a9043e01767c4305bf53852e4e956a75bbf0d338e9bdd84693d854aadb1_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:cffc1a5602bc8275c83aff3a8397dc812b925494deb8105bad675e1eebc1ce4f_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argo-rollouts-rhel8@sha256:f1551e8646b6f845566aa3786194b2cb3392240617ec33a8598e1361a2f7cf6e_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:2959776572015171fe9e674bef16cd27207ad0dd9778597f61c92bd0b68419cb_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:6751efa0700ce5aca7e998b507f2694d36671c800bd3df39c1793fdb79295b01_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:7de02503f35ffa0385273117b00104f7cd13cf62e90236a539b00d0a26914fe5_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-extensions-rhel8@sha256:9628abc742fa7d3e4e7f76c42f86f729a12064b31c6fdcd4d56fd12de42c312d_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:2b613ea76cf38f82b81c0f94bc1310f8221ebfae30e11bb3eb9a9322f7de781c_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:9b2b128beada3283376cb1e0daa09f3074e865cd13feff7e5cf4be22b80b73eb_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:adff90e820d35b5f6edb54e8a3e66a1944b3df7949b82b52757542990532a927_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/argocd-rhel8@sha256:c828786304a861504124f4adcef108a8ec2fbb1ffe39c6f40cbcd45421d9da63_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:23d6aff07ace832a252e24f8c4f50fa7bb8071195266ca2ee1ecb85d2c8cd040_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:7cf81305f51be21dd5044cf2b5e252c3504a5593b25c79efd14ac4c07b845e0e_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:b7729386eafdea2376dd9b95e2f30904f0a737108fa01643425a26817b2d49e3_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/console-plugin-rhel8@sha256:bd66924e532f909e4efe16a7d02556ce50d3aeb399a1c576365c58e28b217156_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:3763f158afee4709f908f9069cafc53e6e19932a89206e1b1c161b83978c8bf3_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:4f556b4a5eb754b8310db23d78984612ce6fb1537a96cf5bba1ca4d9db24c458_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:5322e7c5c3e6648cbc31aef26c793fe446de59f926c9e420e7bbe69be5b7628c_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/dex-rhel8@sha256:575fe0d90e61cd644293c9775b0b6670b159bf0e004b1514f65473a353ed157e_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-operator-bundle@sha256:9233f5165c36e049c07f6c86bc4a330e8cd5c92fdb9e26364f83156e5079a573_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:1ec8b3afca8969bb43413de847e9e42e863a00e618b2d75585a297f605d4c2cd_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:b5bad8e3002354e708978aa81d8fb12ce244336677dd4b43d05a2e3d28ee21fe_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:c11750919f393a494bd39f5430dd64502fda211e1e58b82b12b25c0aefb01b10_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8-operator@sha256:f44ea91f40a80ea0ceb8ce162344632fa4ac83a25e40e3e268a04960dd4cef8e_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:02615dcef407b4c180d2136fd2d0179b75a938663530173c3155fc137158b9ef_ppc64le as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:2fdc37ff27fe77bcf1b49b5067cc29250ec8e1073a1e3d747c46471a12a23bd2_s390x as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:bab70614afc93dde060a53ae72f677c979851881160f434a7b3a82c208122222_amd64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/gitops-rhel8@sha256:bfd4fc073330dff519a73394fd300f304dce3b7d4de1cc741324af08085819e6_arm64 as a component of Red Hat OpenShift GitOps 1.15; openshift-gitops-1/must-gather-rhel8@sha256:a19ac137261209f8d9a0648179637ea7c2a4e0e605c6f1370de6f74deea62676_arm64 as a component of Red Hat OpenShift GitOps 1.15; and 1000 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-4268↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-C6GW-W398-HV78↗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-27144 · cve.blacktree.nl