# Emissary May Use a Broken or Risky Cryptographic Algorithm

Advisory record · `GHSA-hw43-fcmm-3m5g`

- **Identifiers:** `GHSA-hw43-fcmm-3m5g` · `CVE-2025-27508`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 5 Mar 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Mar 2025, 22:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gov.nsa.emissary:emissary` (Maven): affected `<8.24.0`; fixed in `8.24.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Emissary (Maven package gov.nsa.emissary:emissary) versions before 8.24.0 have a ChecksumCalculator class that defaults to SHA-1 and also offers CRC32 and SSDEEP, algorithms unsuitable for security-sensitive uses. The source gives few details about a concrete exploit path; it describes risk if applications rely on these algorithms for integrity or authentication, where collisions could be crafted. Upgrade to version 8.24.0 or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hw43-fcmm-3m5g)

## Sources

- [GitHub Advisory Database: GHSA-hw43-fcmm-3m5g](https://github.com/advisories/GHSA-hw43-fcmm-3m5g)
- [OSV: GHSA-hw43-fcmm-3m5g](https://osv.dev/vulnerability/GHSA-hw43-fcmm-3m5g)
- <https://github.com/NationalSecurityAgency/emissary/security/advisories/GHSA-hw43-fcmm-3m5g>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-27508>
- <https://github.com/NationalSecurityAgency/emissary/commit/da3a81a8977577597ff2a944820a5ae4e9762368>
- <https://github.com/NationalSecurityAgency/emissary>
- <https://github.com/NationalSecurityAgency/emissary/releases/tag/8.24.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hw43-fcmm-3m5g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hw43-fcmm-3m5g/>. Everything for agents: <https://agentprime.io/llms.txt>.