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

Improper Handling of Highly Compressed Data (Data Amplification) in github.com/getkin/kin-openapi/openapi3filter

getkin · kin-openapi

Official source article: GitHub GHSA-WQ9G-9VFC-CFQ9 ↗. Check the applicable product and release in the original source.

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 19 Mar 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.53% 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 getkin kin-openapi and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

5 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-github-getkin-kin-openapiAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-github-getkin-kin-openapiAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-github-getkin-kin-openapiVendor fix publishedDebian records a fixed source-package version for this release.0.135.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-github-getkin-kin-openapiVendor fix publishedDebian records a fixed source-package version for this release.0.135.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-getkin-kin-openapiUnder 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 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
Gogithub.com/getkin/kin-openapiSEMVER: introduced 0; fixed 0.131.00.131.0OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/getkin/kin-openapi< 0.131.00.131.0GitHub advisory ↗upstream repository advisory · 15 May 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-30153 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/getkin/kin-openapi/openapi3filter: Improper Handling of Highly Compressed Data (Data Amplification) in github.com/getkin/kin-openapi/openapi3filter
3 known affected

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

  • acm-flightctl-api-container as a component of Red Hat Edge Manager preview
  • acm-flightctl-worker-container as a component of Red Hat Edge Manager preview
  • flightctl.src as a component of Red Hat Edge Manager preview
Summary
A flaw was found in kin-openapi. This vulnerability allows excessive memory consumption via upload of a crafted ZIP file (a "ZIP bomb").
Remediation
For multicluster engine for Kubernetes, see the following documentation for details on how to install the images: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#mce-install-intro
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-6729

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

kin-openapi is a Go project for handling OpenAPI files. Prior to 0.131.0, when validating a request with a multipart/form-data schema, if the OpenAPI schema allows it, an attacker can upload a crafted ZIP file (e.g., a ZIP bomb), causing the server to consume all available system memory. The root cause comes from the ZipFileBodyDecoder, which is registered automatically by the module (contrary to what the documentation says). This vulnerability is fixed in 0.131.0.

What

kin-openapi is a Go project for handling OpenAPI files. Prior to 0.131.0, when validating a request with a multipart/form-data schema, if the OpenAPI schema allows it, an attacker can upload a crafted ZIP file (e.g., a ZIP bomb), causing the server to consume all available system memory. The root cause comes from the ZipFileBodyDecoder, which is registered automatically by the module (contrary to what the documentation says). This vulnerability is fixed in 0.131.0.

Why

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

kin-openapi is a Go project for handling OpenAPI files. Prior to 0.131.0, when validating a request with a multipart/form-data schema, if the OpenAPI schema allows it, an attacker can upload a crafted ZIP file (e.g., a ZIP bomb), causing the server to consume all available system memory. The root cause comes from the ZipFileBodyDecoder, which is registered automatically by the module (contrary to what the documentation says). This vulnerability is fixed in 0.131.0.

Why

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
a network path → Improper Handling of Highly Compressed Data (Data Amplification) → cause the confidentiality, integrity or availability impact described by the vendor
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-409 ↗

CWE-409: Improper Handling of Highly Compressed Data (Data Amplification). The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

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:N/A:H

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.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-409Public 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-20250326Security Bulletin 26 Mar 2025

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250320Security Bulletin 20 Mar 2025

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

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

d?id=CVE-2025-22872 Référence CVE CVE-2025-24855 https://www.cve.org/CVERecord?id=CVE-2025-24855 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-27553 https://www.cve.org/CVERecord?id=CVE-2025-27553 Référence CVE CVE-2025-28162 https://www.cve.org/CVERecord?id=CVE-2025-28162 Référence CVE CVE-2025-28164 https://www.cve.org/CVERecord?id=CVE-2025-28164 Référence CVE CVE-2025-29774 https://www.cve.org/CVERecord?id=CVE-2025-29774 Référence CVE CVE-2025-29775 https://www.cve.org/CVERecord?id=CVE-2025-29775 Référence CVE CVE-2025-30065 https://www.cve.org/CVERecord?id=CVE-2025-30065 Référence CVE CVE-2025-30153 https://www.cve.org/CVERecord?id=CVE-2025-30153 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 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-37731 https://www.cve.org/CVERecord?id=CVE-2025-37731 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE

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

cord?id=CVE-2025-1594 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 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-22919 https://www.cve.org/CVERecord?id=CVE-2025-22919 Référence CVE CVE-2025-24813 https://www.cve.org/CVERecord?id=CVE-2025-24813 Référence CVE CVE-2025-2759 https://www.cve.org/CVERecord?id=CVE-2025-2759 Référence CVE CVE-2025-30153 https://www.cve.org/CVERecord?id=CVE-2025-30153 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 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-31651 https://www.cve.org/CVERecord?id=CVE-2025-31651 Référence CVE CVE-2025-32988 https://www.cve.org/CVERecord?id=CVE-2025-32988 Référence CVE CVE-2025-32989 https://www.cve.org/CVERecord?id=CVE-2025-32989 Référence CVE CVE-2025-32990 https://www.cve.org/CVERecord?id=CVE-2025-32990 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=C

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

ord?id=CVE-2025-22235 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-23184 https://www.cve.org/CVERecord?id=CVE-2025-23184 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CVE-2025-26791 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-2900 https://www.cve.org/CVERecord?id=CVE-2025-2900 Référence CVE CVE-2025-29927 https://www.cve.org/CVERecord?id=CVE-2025-29927 Référence CVE CVE-2025-30153 https://www.cve.org/CVERecord?id=CVE-2025-30153 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-41232 https://www.cve.org/CVERecord?id=CVE-2025-41232 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-48050 https://www.cve.org/CVERecord?id=CVE-2025-48050 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Gestion détaillée du document le 24 octobre 2025 Version initial

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

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

Evidence and provenance

Published 19 Mar 2025 · Last source change 19 Mar 2025, 18:25 UTC · CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)

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-6729
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 0.131.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 0.131.0 · Fixed: For multicluster engine for Kubernetes, see the following documentation for details on how to install the images: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/clusters/cluster_mce_overview#mce-install-intro
    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 ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-30153 · cve.blacktree.nl