# CVE-2026-109126: IBM Verify Identity Access and IBM Security Verify Access Hard-coded Credentials

> A physically proximate attacker can gain elevated privileges in IBM Verify Access appliances due to hard-coded credentials.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-35w7-m95r-vv83

## What is CVE-2026-109126?

CVE-2026-109126 is a high-severity vulnerability in IBM Security Verify Access, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 Appliance could allow a physically proximate attacker to gain elevated privileges due to the use of hard-coded credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-109126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109126 is a high-severity vulnerability in IBM Security Verify Access, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109126 in the wild and no public exploit code.

Affected product: IBM Security Verify Access. 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-109126/ (Markdown: https://insights.sbomify.com/CVE-2026-109126/index.md)
```

## Sources

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

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