# Keylime registrar is vulnerable to Denial-of-Service attack when updated to version 7.12.0 Advisory record · `GHSA-9jxq-5x44-gx23` - **Identifiers:** `GHSA-9jxq-5x44-gx23` · `CVE-2025-1057` · `PYSEC-2026-1488` - **State:** Confirmed - **Severity:** CVSS 4.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-704](https://cwe.mitre.org/data/definitions/704.html) · [CWE-1287](https://cwe.mitre.org/data/definitions/1287.html) - **Tags:** [CWE-704](https://agentprime.io/advisories/tag/cwe-704.md) · [CWE-1287](https://agentprime.io/advisories/tag/cwe-1287.md) - **Published:** 14 Feb 2025 - **Updated:** 21 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 14 Feb 2025, 18:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `keylime` (PyPI): affected `>=7.12.0, <7.12.1`; fixed in `7.12.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Keylime registrar versions >=7.12.0, <7.12.1 are vulnerable to a denial-of-service attack after an update. Version 7.12.0 rejects database data stored by versions 7.8.0 and later, so an attacker who registered many agents with different UUIDs before the update can make queries against those entries fail. Upgrade to Keylime 7.12.1 or later. As a workaround, remove the registrar database and re-register all agents. 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 - 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.0040, the 34th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 15 Mar 2025, 08:50 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-1057) - 15 Mar 2025, 09:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-1057) - 31 Oct 2026, 14:42 UTC: First seen by agentprime - 31 Oct 2026, 14:42 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9jxq-5x44-gx23) ## Sources - [GitHub Advisory Database: GHSA-9jxq-5x44-gx23](https://github.com/advisories/GHSA-9jxq-5x44-gx23) - [OSV: GHSA-9jxq-5x44-gx23](https://osv.dev/vulnerability/GHSA-9jxq-5x44-gx23) - - - - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .