> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/keeper-secrets-manager/2026/rust-sdk-17.4.0.md).

# Rust SDK 17.4.0

Released on November 11, 2026

> **Breaking changes**
>
> **KSM-1767:** The `p256` and `ecdsa` types in the public API are now the `p256` 0.14 and `ecdsa` 0.17 types. They appear in the `CryptoUtils` key generation and parsing functions, `sign_data`, and `decrypt_ec`, and in `EncryptedPayload`. Code that names these types, uses its own `p256` or `ecdsa` traits on them, or passes its own `p256` keys must use the same versions. Method calls on the returned keys can also need a change, even if your code does not depend on `p256` directly. For example, `to_encoded_point` is now `to_sec1_point`. Run `cargo update`. For a `ctutils` conflict or a Rust 1.87 build, see [Upgrading to 17.4.0](https://docs.keeper.io/spaces/-MJXOXEifAmpyvNVL1to/pages/1JFzdiWvr90N0iJeH1fP#upgrading-to-17.4.0).

### Security

* **KSM-1767:** Updated `p256` to 0.14 and `ecdsa` to 0.17. This moves the transitive dependency `crypto-bigint` from 0.5.5 to 0.7.10 and resolves [RUSTSEC-2026-0387](https://rustsec.org/advisories/RUSTSEC-2026-0387.html). The advisory reports that some `crypto-bigint` operations meant to run in constant time can take secret-dependent branches, depending on the compiler and CPU. The fix needs the new `p256` line, so this release changes public types (see Breaking changes). Public keys and ECDH results do not change. ECDSA signatures also stay the same, except for about 1 in 4 billion messages, where this release follows RFC 6979 exactly. Both forms are valid. The private key parser now rejects two malformed key forms that common key tools do not write. `public_encrypt`, `encrypt_aes_gcm`, and `encrypt_aes_cbc` now return an error instead of panicking when the OS random number generator fails.
* **KSM-1766:** Updated the locked dependencies `rustls`, `rustls-webpki`, `webpki-root-certs`, `quinn-proto`, `h2`, `tokio`, and `anyhow` to current releases, which include advisory fixes and a refreshed root certificate list. Cargo ignores a library's lock file. Run `cargo update` in your project to get these versions.

### **Resources**

* [Crates.io package](https://crates.io/crates/keeper-secrets-manager-core/17.4.0)
* [docs.rs](https://docs.rs/keeper-secrets-manager-core/17.4.0)
* [Rust SDK Documentation](https://docs.keeper.io/keeperpam/secrets-manager/developer-sdk-library/rust-sdk.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/enterprise/keeper-secrets-manager/2026/rust-sdk-17.4.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
