Cyber Resilience

CVE-2025-7339

Published
17 July 2025
Modified
17 June 2026
CVSS Score v3.1 3.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0017 7th percentile
Risk Priority 27 floored blend · peak EPSS

Summary

CVE-2025-7339 is a low-severity Improper Handling of Unexpected Data Type (CWE-241) vulnerability in Openjsf (inferred from references). Its CVSS base score is 3.4 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

on-headers is a node.js middleware for listening to when a response writes headers. A bug in on-headers versions `<1.1.0` may result in response headers being inadvertently modified when an array is passed to `response.writeHead()`. Users should upgrade to version 1.1.0…

more

to receive a patch. Uses are strongly encouraged to upgrade to `1.1.0`, but this issue can be worked around by passing an object to `response.writeHead()` rather than an array.

CWE(s)
CWE-241

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9423Shared CWE-241
CVE-2025-63548Shared CWE-241
CVE-2025-1004Shared CWE-241
CVE-2024-25966Shared CWE-241
CVE-2024-21935Shared CWE-241
CVE-2025-2268Shared CWE-241
CVE-2024-0151Shared CWE-241
CVE-2024-32268Shared CWE-241
CVE-2026-47110Shared CWE-241
CVE-2024-37316Shared CWE-241

Affected Assets

Openjsf
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation explicitly checks that supplied data matches expected types and rejects mismatches before they reach processing logic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and type checking to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-handling flaws but does not itself implement the preventive control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and type checking that directly mitigates improper handling of unexpected data types.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate strong input validation and type enforcement to prevent malformed data processing.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles encourage robust input handling but do not specifically address data-type validation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require type checking and input sanitization, directly addressing improper handling of unexpected data types.

References