# CVE-2026-13260: Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify Access

> Remote attackers can cause denial of service in IBM Verify Identity Access due to insufficient validation of incoming request resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-cvqh-9j59-vmc5

## What is CVE-2026-13260?

CVE-2026-13260 is a high-severity denial of service vulnerability in IBM Security Verify Access, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Verify Identity Access could allow a remote attacker to cause a denial of service due to insufficient validation of incoming request resources.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-13260 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13260 is a high-severity denial of service vulnerability in IBM Security Verify Access, published on 14 Sep 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-13260 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-13260/ (Markdown: https://insights.sbomify.com/CVE-2026-13260/index.md)
```

## Sources

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

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