# RUSTSEC-2026-0286: Out-of-bounds read when decoding CKA_ALLOWED_MECHANISMS

> An out-of-bounds read in the cryptoki library allows attackers to cause crashes or disclose heap memory via crafted PKCS#11 attributes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Also known as:** GHSA-r6vc-97x9-63vv

## What is RUSTSEC-2026-0286?

RUSTSEC-2026-0286 is a memory corruption vulnerability in cryptoki, published on 16 Sep 2026. 

### Official description

`cryptoki` treated the CKA_ALLOWED_MECHANISMS ulValueLen byte count as a
CK_MECHANISM_TYPE element count. A valid nonempty attribute returned through
the safe `Session::get_attributes` API could cause construction of an
out-of-bounds slice and undefined behavior.

Possible consequences include a process crash or denial of service and
potential disclosure of adjacent heap words. Upgrade to the fixed patch release
for the cryptoki 0.10, 0.11, or 0.12 line.

## Which versions are affected by RUSTSEC-2026-0286?

1 open source package ship an affected version, including cryptoki.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cryptoki` | crates.io | From 0.0.0-0 | 0.10.1, 0.11.1, 0.12.1 |

## How do I fix RUSTSEC-2026-0286?

Upgrade cryptoki to a fixed version for your release line: 0.10.1, 0.11.1 or 0.12.1.

## Is RUSTSEC-2026-0286 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0286 and fix it if it is affected.

What it is: RUSTSEC-2026-0286 is a memory corruption vulnerability in cryptoki, published on 16 Sep 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0286 in the wild and no public exploit code.

Affected packages and fixed versions:
- cryptoki (crates.io): affected from 0.0.0-0; fixed in 0.10.1, 0.11.1, 0.12.1

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/RUSTSEC-2026-0286/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0286/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0286

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