Skip to content
Fencer Intel
no cvss —

GHSA-r6vc-97x9-63vv json

Out-of-bounds read when decoding CKA_ALLOWED_MECHANISMS

published last mo. modified last mo. also RUSTSEC-2026-0286

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

`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.

Patch / fix

  • crates.io cryptoki 0.10.1, 0.11.1, 0.12.1

Is GHSA-r6vc-97x9-63vv in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io cryptoki
>=0.0.0-0, <0.10.1
>=0.11.0, <0.11.1
>=0.12.0, <0.12.1
0.10.1
0.11.1
0.12.1

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.