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.42% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-31808High confidence
file-type affected by infinite loop in ASF parser on malformed input with zero-size sub-header
sindresorhus · file-type
Official source article: GitHub GHSA-5V7R-6R5C-R473 ↗. Check the applicable product and release in the original source.
5.3MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
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
- Confirm that the asset runs sindresorhus file-type and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 16 affected or under-investigation product states without a fixed product state in the same current advisory
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 package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmfile-type | >= 13.0.0, < 21.3.1 | 21.3.1 | GitHub advisory ↗upstream repository advisory · 10 Mar 2026 |
| npmfile-type | SEMVER: introduced 13.0.0; fixed 21.3.1 | 21.3.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
1 currentAuthoritative 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.
CVE-2026-31808 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityfile-type: file-type: Denial of Service due to infinite loop in ASF file parsing
The vendor explicitly identifies these products as affected by this CVE.
- io.cryostat-cryostat as a component of Cryostat 4
- openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch6-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/logging-curator5-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- io.apicurio-apicurio-registry as a component of Red Hat build of Apicurio Registry 2
- org.infinispan-infinispan-console as a component of Red Hat Data Grid 8
- rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
- rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- Summary
- A flaw was found in file-type, a library for detecting file types. A remote attacker can exploit this by providing a specially crafted ASF (Advanced Systems Format) file. When parsing the file, a zero-sized sub-header can trigger an infinite loop, leading to a Denial of Service (DoS). This can stall the Node.js event loop, preventing the application from processing further requests.
- Remediation
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 16 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
file-type detects the file type of a file, stream, or data. Prior to 21.3.1, a denial of service vulnerability exists in the ASF (WMV/WMA) file type detection parser. When parsing a crafted input where an ASF sub-header has a size field of zero, the parser enters an infinite loop. The payload value becomes negative (-24), causing tokenizer.ignore(payload) to move the read position backwards, so the same sub-header is read repeatedly forever. Any application that uses file-type to detect the type of untrusted/attacker-controlled input is affected. An attacker can stall the Node.js event loop with a 55-byte payload. Fixed in version 21.3.1.
What
file-type detects the file type of a file, stream, or data. Prior to 21.3.1, a denial of service vulnerability exists in the ASF (WMV/WMA) file type detection parser. When parsing a crafted input where an ASF sub-header has a size field of zero, the parser enters an infinite loop. The payload value becomes negative (-24), causing tokenizer.ignore(payload) to move the read position backwards, so the same sub-header is read repeatedly forever. Any application that uses file-type to detect the type of untrusted/attacker-controlled input is affected. An attacker can stall the Node.js event loop with a 55-byte payload. Fixed in version 21.3.1.
Why
A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.
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
file-type detects the file type of a file, stream, or data. Prior to 21.3.1, a denial of service vulnerability exists in the ASF (WMV/WMA) file type detection parser. When parsing a crafted input where an ASF sub-header has a size field of zero, the parser enters an infinite loop. The payload value becomes negative (-24), causing tokenizer.ignore(payload) to move the read position backwards, so the same sub-header is read repeatedly forever. Any application that uses file-type to detect the type of untrusted/attacker-controlled input is affected. An attacker can stall the Node.js event loop with a 55-byte payload. Fixed in version 21.3.1.
Why
A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.
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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Loop with Unreachable Exit Condition ('Infinite Loop') → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-835 ↗
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'). The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
- 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:LCommon 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.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
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
- io.cryostat-cryostat as a component of Cryostat 4
- openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/elasticsearch6-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/logging-curator5-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- io.apicurio-apicurio-registry as a component of Red Hat build of Apicurio Registry 2
- org.infinispan-infinispan-console as a component of Red Hat Data Grid 8
- rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
- rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- devspaces/code-rhel9 as a component of Red Hat OpenShift Dev Spaces
- devspaces/code-sshd-rhel9 as a component of Red Hat OpenShift Dev Spaces
- satellite/iop-host-inventory-frontend-rhel9 as a component of Red Hat Satellite 6
- ansible-automation-platform/automation-portal as a component of Self-service automation portal 2
- Fixed
- 21.3.1.
- 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
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04
Evidence and provenance
Published 10 Mar 2026 · Last source change 11 Mar 2026, 16:00 UTC · CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-10894
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
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.