# CVE-2026-3482: IBM Sterling B2B Integrator and IBM Sterling File Gateway Authorization Bypass

> Unauthenticated attackers can bypass authentication via crafted HTTP requests to read sensitive information in IBM Sterling B2B Integrator and File Gateway.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-qp9j-9ffq-4c7v

## What is CVE-2026-3482?

CVE-2026-3482 is a medium-severity authentication bypass vulnerability in Ibm Sterling B2b Integrator, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.2.0.0 through 6.2.0.5_2,  6.2.1.0 through 6.2.1.1_2, and  6.2.2.0 through 6.2.2.0_1 could allow an unauthenticated user to read sensitive information by bypassing authentication through a specially crafted HTTP request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 2 products.


Products: Ibm Sterling B2b Integrator, Ibm Sterling File Gateway.

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

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

## Is CVE-2026-3482 being exploited?

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

## Other vulnerabilities in Ibm Sterling B2b Integrator

- [CVE-2015-7450](https://insights.sbomify.com/CVE-2015-7450/): IBM WebSphere Application Server and Server Hypervisor Edition Code Injection. (critical 9.8, exploited in the wild)
- [CVE-2024-31903](https://insights.sbomify.com/CVE-2024-31903/): IBM Sterling B2B Integrator Standard Edition code execution (high 8.8)
- [CVE-2019-4728](https://insights.sbomify.com/CVE-2019-4728/): Deserialization in Sterling B2B Integrator (high 8.8)
- [CVE-2020-4762](https://insights.sbomify.com/CVE-2020-4762/): Privilege escalation in Sterling B2B Integrator (high 8.8)
- [CVE-2017-1174](https://insights.sbomify.com/CVE-2017-1174/): SQL injection in Sterling B2B Integrator (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3482 is a medium-severity authentication bypass vulnerability in Ibm Sterling B2b Integrator, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3482 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-3482/ (Markdown: https://insights.sbomify.com/CVE-2026-3482/index.md)
```

## Sources

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

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