Unauthenticated response poisoning via unvalidated Host header
Published Jun 11, 2026 · Updated Jun 11, 2026
HTTP header injection in IBM DevOps Plan 3.0.0 through 3.0.6 allows remote attackers to poison responses via the Host header. The Host-processing path accepts an attacker-controlled Host value without adequate validation before it influences generated HTTP headers, but IBM has not named the handler or response field. No authentication or user interaction is required; crafted values can enable cross-site scripting, cache poisoning, or session hijacking.
Summary
What happened
HTTP header injection in IBM DevOps Plan 3.0.0 through 3.0.6 allows remote attackers to poison responses via the Host header. The Host-processing path accepts an attacker-controlled Host value without adequate validation before it influences generated HTTP headers, but IBM has not named the handler or response field. No authentication or user interaction is required; crafted values can enable cross-site scripting, cache poisoning, or session hijacking.
The record
- CVE
- CVE-2026-4096
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- OpenBMC Project
- Product
- DevOps Plan
- Classifications
- CWE-644, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record 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=3.0.0 <=3.0.6
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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