CVE-2026-4364
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 · uneditedIBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 allows certificate listings retrieved via a browser session to return a JSON payload while incorrectly specifying the response Content-Type as text/html. Because the content is delivered with an HTML MIME type, browsers may interpret the JSON data as executable script under certain conditions. This creates an opportunity for JavaScript injection, potentially leading to cross-site scripting (XSS).
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 confidenceIBM Verify Identity Access and Security Verify Access versions 10.0-10.0.9.1 and 11.0-11.0.2 return certificate listing data as JSON but incorrectly set the Content-Type header to text/html instead of application/json. Because browsers receive an HTML MIME type, they may parse the JSON payload as executable HTML content, enabling JavaScript injection and stored cross-site scripting (XSS) when the response is rendered in a browser session.
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>= 10.0.0.0, <= 10.0.9.1>= 10.0.0.0, <= 10.0.9.1>= 11.0.0.0, <= 11.0.2.0>= 11.0.0.0, <= 11.0.2.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify the installed IBM Verify Access versionUse the product's admin interface, command-line tool, or check the product documentation to determine the exact version number of IBM Security Verify Access or IBM Verify Identity AccessAffected if The installed version falls within 10.0.0.0-10.0.9.1 or 11.0.0.0-11.0.2.0
-
Locate the certificate listing API endpointIdentify the API endpoint that returns certificate listing data - this is typically a REST API endpoint within the product's management or administration interfaceAffected if The endpoint exists and returns certificate data as JSON
-
Capture the response headers from the certificate endpointMake an authenticated HTTP request to the certificate listing endpoint and inspect the Content-Type header in the responseAffected if The Content-Type header is set to text/html when the response body contains JSON data
-
Verify the response body formatExamine the HTTP response body from the certificate listing endpoint to confirm it contains JSON-formatted certificate dataAffected if The response body is valid JSON but was served with an incorrect Content-Type
-
Confirm XSS vulnerability potentialIf JSON data is served with text/html Content-Type, verify that the JSON payload could contain malicious script content that a browser would execute as HTMLAffected if The JSON response contains data that could be interpreted as executable HTML script tags
You are affected if your installed version is between 10.0.0.0-10.0.9.1 or 11.0.0.0-11.0.2.0 AND the certificate listing endpoint returns JSON data with a text/html Content-Type header.
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.
From vendor dataConfigure all API endpoints serving JSON data to return the correct Content-Type header (application/json). Additionally, implement Content Security Policy (CSP) headers and validate/sanitize output to prevent XSS exploitation.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4364 — 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-2026-4364 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