dbcve.org
Devops PlanApplication · Hcltech

CVE-2026-4096

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 3.0.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM DevOps Plan 3.0.0 through 3.0.6 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM DevOps Plan versions 3.0.0 through 3.0.6 fails to properly validate HOST header input, allowing attackers to inject arbitrary HTTP headers. This can lead to XSS attacks via header reflection, cache poisoning where malicious content gets cached, and session hijacking through cookie manipulation or header-based session fixation.

MitigationImplement strict validation and sanitization of the HOST header server-side, using an allowlist of permitted values and normalizing/canonicalizing the header before use. Additionally, configure the application server to reject requests with unexpected HOST values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Devops PlanApplication
Affected:>= 3.0.0, < 3.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM DevOps Plan version
    Locate the version information for your IBM DevOps Plan installation. This is typically found in the product's about page, installation directory, or by querying the product's built-in version endpoint if available. Common locations include the installation root folder or the administration console.
    Affected if The installed version is 3.0.0 through 3.0.6 (any version >= 3.0.0 but < 3.0.7)
  2. Confirm the application accepts HTTP/HTTPS connections
    Verify that the IBM DevOps Plan web interface or API is accessible over HTTP or HTTPS. Check your network configuration, reverse proxy settings, or firewall rules to confirm the product is exposed as a web service.
    Affected if The product is running and accepting HTTP/HTTPS requests where it processes incoming HOST headers
  3. Test for HOST header injection vulnerability
    Send a crafted HTTP request to the IBM DevOps Plan endpoint with a manipulated HOST header (e.g., HOST: example.com%0D%0AX-Injected-Header: value) and observe whether the injected header is reflected in the response or processed by the server.
    Affected if The server accepts and processes the manipulated HOST header without validation, allowing header injection
  4. Review HTTP request handling configuration
    Examine the IBM DevOps Plan configuration files or web server settings to determine how HOST headers are processed. Look for any proxy or middleware configurations that pass HOST headers to the backend without sanitization.
    Affected if The configuration allows raw HOST header values to be passed through to the application without validation

Your environment is affected if IBM DevOps Plan version 3.0.0-3.0.6 is installed and the web interface is accessible over HTTP/HTTPS, allowing unvalidated HOST headers to be processed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.7 or later
Fixed in 3.0.7
Interim mitigation

Implement strict validation and sanitization of the HOST header server-side, using an allowlist of permitted values and normalizing/canonicalizing the header before use. Additionally, configure the application server to reject requests with unexpected HOST values.

Recommended fix High confidence

IBM DevOps Plan 3.0.7

  1. 1. Plan an upgrade window for the IBM DevOps Plan installation
  2. 2. Back up the current IBM DevOps Plan installation, including configuration files and data
  3. 3. Upgrade IBM DevOps Plan from version 3.0.0-3.0.6 to version 3.0.7 or later
  4. 4. After the upgrade, verify the installation was successful and all services are running
  5. 5. Test that the HOST header handling works correctly and the HTTP header injection vulnerability is resolved
  6. 6. Monitor IBM security advisories for any subsequent security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devops Plan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4096 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data