# CVE-2026-19273: The Dashboard of IBM Sterling B2B Integrator and IBM Sterling File Gateway are Vulnerable to Improper Access Control

> Remote authenticated attackers can bypass security restrictions in the Dashboard of IBM Sterling B2B Integrator and File Gateway due to improper authentication.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-8f75-86xx-87vh

## What is CVE-2026-19273?

CVE-2026-19273 is a medium-severity authentication bypass vulnerability in IBM Sterling B2B Integrator, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Sterling B2B Integrator 6.2.0.0 through 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1 and IBM Sterling File Gateway 6.2.0.0 through 6.2.0.6_2, 6.2.1.0 - 6.2.1.2, 6.2.2.0 - 6.2.2.1 Standard Edition could allow a remote authenticated attacker to bypass security restrictions due to improper authentication.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-19273?


## How do I fix CVE-2026-19273?

No fix has been published for CVE-2026-19273 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19273 being exploited?

There is no known exploitation of CVE-2026-19273 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19273 and fix it if it is affected.

What it is: CVE-2026-19273 is a medium-severity authentication bypass vulnerability in IBM Sterling B2B Integrator, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19273 in the wild and no public exploit code.

Affected product: IBM Sterling B2B Integrator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19273/ (Markdown: https://insights.sbomify.com/CVE-2026-19273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19273
- OSV: https://osv.dev/vulnerability/CVE-2026-19273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19273/
Summaries are generated and may contain mistakes; the official description above is the record.