RUSTSEC-2026-0273
Vulnerability from osv_rustsec – Published: 2026-04-07 12:00 – Updated: 2026-09-09 08:26 – Source websiteThe 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 READMEs make no hint at the fact that the SecureEnclaveSigner 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.
{
"affected": [
{
"database_specific": {
"categories": [
"crypto-failure"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"manzana::secure_enclave::SecureEnclaveSigner::create",
"manzana::secure_enclave::SecureEnclaveSigner::delete",
"manzana::secure_enclave::SecureEnclaveSigner::load",
"manzana::secure_enclave::SecureEnclaveSigner::sign",
"manzana::secure_enclave::SecureEnclaveSigner::verify"
],
"os": [
"macos"
]
}
},
"package": {
"ecosystem": "crates.io",
"name": "manzana",
"purl": "pkg:cargo/manzana"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.3.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "The `manzana` crate appears to be a work-in-progress module for the Apple Silicon chips\u0027 features, including the Secure Enclave.\n\nThis crate\u0027s 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.\n\nUnsuspecting 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.\n\nThere 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.",
"id": "RUSTSEC-2026-0273",
"modified": "2026-09-09T08:26:17Z",
"published": "2026-04-07T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/manzana"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0273.html"
},
{
"type": "REPORT",
"url": "https://github.com/paiml/manzana/issues/3"
},
{
"type": "WEB",
"url": "https://github.com/paiml/manzana/blob/89e3183ac38088d418a2edeb9d3e0f35133b27a3/README.md"
},
{
"type": "WEB",
"url": "https://github.com/paiml/manzana/blob/89e3183ac38088d418a2edeb9d3e0f35133b27a3/src/secure_enclave.rs#L312"
},
{
"type": "WEB",
"url": "https://github.com/paiml/manzana/blob/89e3183ac38088d418a2edeb9d3e0f35133b27a3/src/secure_enclave.rs#L352"
}
],
"related": [],
"severity": [],
"summary": "Stubbed cryptography without warnings"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.