# RUSTSEC-2026-0273: Stubbed cryptography without warnings

> The manzana crate provides a stubbed Secure Enclave signer that returns fixed values, misleading users into believing they have secure cryptographic operations.

- **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:** 7 Apr 2026

## What is RUSTSEC-2026-0273?

RUSTSEC-2026-0273 is a vulnerability in manzana, published on 7 Apr 2026. 

### Official description

The `manzana` crate appears to be a work-in-progress module for the Apple Silicon chips' features, including the Secure Enclave.

This crate's description and `README`s make no hint at the fact that the [`SecureEnclaveSigner`](https://docs.rs/manzana/0.2.0/manzana/secure_enclave/struct.SecureEnclaveSigner.html) type is a stubbed implementation that does not actually perform any cryptographic operations, and instead returns fixed values.

Unsuspecting users of the crate, who may not check the source code, receive no warning about this and may believe they are using a secure implementation when they are not.

There are currently (as of `2026-04-07`) no versions of the crate that contain either a real implementation, or a warning about the stubbed cryptography.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `manzana` | crates.io | From 0.0.0-0 | 0.3.0 |

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

Upgrade manzana to 0.3.0 or later.

## Is RUSTSEC-2026-0273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0273 is a vulnerability in manzana, published on 7 Apr 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0273 in the wild and no public exploit code.

Affected packages and fixed versions:
- manzana (crates.io): affected from 0.0.0-0; fixed in 0.3.0

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

## Sources

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

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