CVE-2026-0835
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 Sterling B2B Integrator and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 are vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
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 confidenceThis is a stored (persistent) cross-site scripting (XSS) vulnerability in the Web UI of IBM Sterling B2B Integrator and IBM Sterling File Gateway. An authenticated attacker can inject malicious JavaScript code into web application input fields, which then executes in the browsers of other users viewing that content, potentially stealing session credentials.
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>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.2.0>= 6.1.0.0, < 6.1.2.8>= 6.2.0.0, < 6.2.0.5_2>= 6.2.1.0, < 6.2.1.1_2= 6.2.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 installed product and versionLocate the IBM Sterling installation directory and check the version file or use the administrative console to view product version informationAffected if The installed version falls within any of the affected ranges: 6.1.0.0-6.1.2.7_2, 6.2.0.0-6.2.0.5_1, 6.2.1.0-6.2.1.1_1, or equals 6.2.2.0
-
Confirm Web UI is accessibleAttempt to access the Web UI login page via HTTP/HTTPS at the typical path (such as / SterlingAPIS / or the application's root URL)Affected if The Web UI is reachable and accepts authentication credentials, indicating the attack surface exists
-
Verify user authentication is enabledCheck the authentication configuration settings within the IBM Sterling administration console or configuration files to confirm user login is not disabledAffected if Authentication is enabled and users can log in, meaning an authenticated attacker could potentially inject malicious script
-
Identify input fields in Web UILog into the Web UI and navigate to common input areas such as partner profiles, trading partner configuration, or notification settings where user-supplied data is storedAffected if Input fields that accept and store user-provided text are present and displayed to other users, creating the conditions for stored XSS
Your environment is affected if you are running any version of IBM Sterling B2B Integrator or IBM Sterling File Gateway within the listed ranges AND the Web UI is accessible with authentication enabled.
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 · scoped6.1.2.86.2.0.5_26.2.1.1_2
Apply vendor-provided patches for the specific versions (6.1.0.0-6.1.2.7_2, 6.2.0.0-6.2.0.5_1, 6.2.1.0-6.2.1.1_1, 6.2.2.0). Until patched, disable or limit user access to the Web UI and implement Content Security Policy headers to mitigate XSS execution.
Sterling B2B Integrator: 6.1.2.8, 6.2.0.5_2, 6.2.1.1_2, or later releases | Sterling File Gateway: 6.1.2.8, 6.2.0.5_2, 6.2.1.1_2, or later releases
- 1. Identify the currently installed version of IBM Sterling B2B Integrator and/or Sterling File Gateway using the system administration console or version lookup utility
- 2. For Sterling B2B Integrator: If running 6.1.0.0-6.1.2.7_2, upgrade to version 6.1.2.8 or later
- 3. For Sterling B2B Integrator: If running 6.2.0.0-6.2.0.5_1, upgrade to version 6.2.0.5_2 or later
- 4. For Sterling B2B Integrator: If running 6.2.1.0-6.2.1.1_1, upgrade to version 6.2.1.1_2 or later
- 5. For Sterling B2B Integrator: If running 6.2.2.0, upgrade to the next available fixed release (e.g., 6.2.2.1 or later)
- 6. Apply the same version mapping for Sterling File Gateway installations
- 7. After upgrade, verify the fix by testing that the Web UI properly sanitizes user inputs and blocks XSS payloads
- 8. Review IBM's upgrade documentation for any prerequisite steps, database migrations, or configuration changes required for your specific version jump
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0835 — 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-0835 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