CVE-2025-3026
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 · uneditedThe vulnerability exists in the EJBCA service, version 8.0 Enterprise. Not tested in higher versions. By modifying the ‘Host’ header in an HTTP request, it is possible to manipulate the generated links and thus redirect the client to a different base URL. In this way, an attacker could insert his own server for the client to send HTTP requests, provided he succeeds in exploiting it.
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 · high confidenceHost Header Injection vulnerability in EJBCA Enterprise 8.0. An unauthenticated attacker can manipulate the HTTP Host header to influence generated links and redirect users to attacker-controlled URLs. This allows credential theft or further attacks via poisoned links.
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>= 8.0, < 9.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EJBCA installationLocate the EJBCA installation directory. On Linux/Unix, check common paths like /opt/ejbca, /usr/local/ejbca, or the application server directory (e.g., /opt/wildfly/standalone/deployments/). On Windows, check C:\Program Files\ejbca or the application server paths. Look for ejbca.ear or ejbca.war files.Affected if EJBCA is not found in the environment, then this CVE does not apply.
-
Identify EJBCA versionCheck the version file or the WAR/EAR manifest. In the EJBCA distribution, look for a version.properties or check the filename of the deployed ejbca.ear. Alternatively, access the EJBCA admin web interface and check the 'About' or 'System Configuration' page for the version number.Affected if The installed version is greater than or equal to 8.0 AND less than 9.1.
-
Verify web server Host header handlingExamine the web server configuration (Apache, Nginx, or the embedded application server like WildFly/JBoss). Look for directives that validate or restrict the Host header, such as Apache's mod_headers configuration, Nginx's valid_referers, or application server servlet filter settings.Affected if No server-side allowlist validation of Host headers is configured, meaning any Host value is accepted.
-
Test for Host header injection vulnerabilitySend an HTTP request to the EJBCA application with a manipulated Host header (e.g., Host: attacker.com) and observe whether the response contains links or redirects pointing to the attacker-controlled domain. Use a tool like curl: curl -H 'Host: malicious.example.com' https://your-ejbca-server/Affected if Generated links, password reset URLs, or redirect locations in the response reflect the injected Host header value.
You are affected if EJBCA is installed with version 8.0 through 9.0.x and the web server does not validate Host headers against an allowlist.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1
Implement server-side validation of Host headers using an allowlist, configure the web server to reject invalid Host values, and use absolute URLs in application responses rather than relative paths.
9.1 or later
- Upgrade EJBCA to version 9.1 or later to resolve the Host header injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-3026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3026 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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