Header manipulation via flat-array misinterpretation
Published Jul 17, 2025 · Updated Jul 17, 2025
Improper array handling in on-headers before 1.1.0 allows local users to alter HTTP response headers through response.writeHead(). The setHeadersFromArray function treats a supported flat key-value array as a two-dimensional array, passing individual characters to setHeader as names and values. Exploitation requires high privileges and an application path that supplies array-form headers while the middleware wraps writeHead; consequences are limited to header integrity and disclosure.
Summary
What happened
Improper array handling in on-headers before 1.1.0 allows local users to alter HTTP response headers through response.writeHead(). The setHeadersFromArray function treats a supported flat key-value array as a two-dimensional array, passing individual characters to setHeader as names and values. Exploitation requires high privileges and an application path that supplies array-form headers while the middleware wraps writeHead; consequences are limited to header integrity and disclosure.
The record
- CVE
- CVE-2025-7339
- Published
- Jul 17, 2025
- Updated
- Jul 17, 2025
- Vendor
- jshttp
- Product
- on-headers
- Classifications
- CWE-241, T1565.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 17, 2025CVE publishedPublication date reported by the CVE source.
- Jul 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Issue 15 response-header array reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo