CVE-2026-1014
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 InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to exposure of sensitive information via JSON server response manipulation.
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 InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6 contains a vulnerability that allows attackers to manipulate JSON server responses to gain access to sensitive information. The flaw likely involves insecure handling of JSON endpoints where authorization or data filtering is insufficient, allowing unauthorized data to be included in API responses.
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>= 11.7.0.0, <= 11.7.1.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Verify IBM InfoSphere Information Server versionCheck the installed version of IBM InfoSphere Information Server using the system inventory or version command provided by IBM (such as 'omVersion' or the IBM InfoSphere Administration Console). Compare the version number to the affected range: 11.7.0.0 through 11.7.1.6.Affected if The installed version falls within 11.7.0.0 to 11.7.1.6 inclusive.
-
Identify accessible JSON API endpointsReview the server configuration or API documentation to determine which JSON endpoints are exposed. Common paths may include endpoints under '/json/', '/api/json/', or similar URL patterns. Use web scanner or manual browser inspection to confirm endpoint availability.Affected if JSON API endpoints are exposed and accessible over the network without additional authentication barriers.
-
Test JSON endpoint authorization controlsSend HTTP requests to the JSON endpoints with and without valid authentication credentials. Observe whether the server returns the same or different data to unauthenticated versus authenticated requests.Affected if Unauthenticated or low-privilege requests to JSON endpoints return sensitive data that should be restricted to authorized users.
-
Inspect JSON response data for information leakageMake requests to JSON endpoints and examine the response payloads. Check whether the JSON responses contain data that the requesting user should not have access to, such as records from other users, internal system information, or privileged data.Affected if JSON responses contain sensitive or unauthorized data that should be filtered based on user permissions.
A user is affected if their IBM InfoSphere Information Server version is between 11.7.0.0 and 11.7.1.6 and JSON API endpoints are accessible without proper authorization controls, allowing unauthorized data exposure.
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 dataApply the vendor-supplied patch for this vulnerability. If no patch is available, restrict network access to the JSON API endpoints and implement proper server-side authorization checks for all JSON response data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1014 — 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-1014 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