# Lemur: Incomplete fix for GHSA-v2wp-frmc-5q3v -- ACME authority update endpoint allows non-admin to replace \`acme_url\` with internal IP, bypassing allowlist

Advisory record · `GHSA-v5rc-cpwc-cfpr`

- **Identifiers:** `GHSA-v5rc-cpwc-cfpr` · `CVE-2026-71303` · `PYSEC-2026-3679`
- **State:** Confirmed
- **Severity:** CVSS 7.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Aug 2026, 20:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `lemur` (PyPI): affected `<1.9.3`; fixed in `1.9.3`

## Machine-written summary

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

> Lemur versions before 1.9.3 are affected. An authenticated user who has been granted membership in an ACME authority's role can change that authority's acme_url through the update endpoint, which skips the host allowlist check applied at creation. When certificates are later issued through that authority, Lemur's backend requests the attacker-chosen URL, which enables server-side request forgery against internal services and cloud metadata endpoints. Upgrade to Lemur 1.9.3.

Written 5 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.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:39 UTC: First seen by agentprime
- 31 Oct 2026, 14:39 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v5rc-cpwc-cfpr)

## Sources

- [GitHub Advisory Database: GHSA-v5rc-cpwc-cfpr](https://github.com/advisories/GHSA-v5rc-cpwc-cfpr)
- [OSV: GHSA-v5rc-cpwc-cfpr](https://osv.dev/vulnerability/GHSA-v5rc-cpwc-cfpr)
- <https://github.com/Netflix/lemur/security/advisories/GHSA-v5rc-cpwc-cfpr>
- <https://github.com/Netflix/lemur/commit/edca0390f930344d65ff4ca37a669c2320e3dfad>
- <https://github.com/Netflix/lemur>
- <https://github.com/Netflix/lemur/releases/tag/v1.9.3>

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-v5rc-cpwc-cfpr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v5rc-cpwc-cfpr/>. Everything for agents: <https://agentprime.io/llms.txt>.
