CVE-2025-1057
Keylime: keylime registrar dos due to incompatible database entry handling
A flaw was found in Keylime, a remote attestation solution, where strict type checking introduced in version 7.12.0 prevents the registrar from reading database entries created by previous versions, for example, 7.11.0. Specifically, older versions store agent registration data as bytes, whereas the updated registrar expects str. This issue leads to an exception when processing agent registration requests, causing the agent to fail.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Exploit likelihood
What each source reports
CVE List Score used
4.3
Keylime: keylime registrar dos due to incompatible database entry handling
A flaw was found in Keylime, a remote attestation solution, where strict type checking introduced in version 7.12.0 prevents the registrar from reading database entries created by previous versions, for example, 7.11.0. Specifically, older versions store agent registration data as bytes, whereas the updated registrar expects str. This issue leads to an exception when processing agent registration requests, causing the agent to fail.
- Record
CVE-2025-1057- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-704
- Updated
- 2026-11-05
EUVDEUVD-2025-4900
4.3
A flaw was found in Keylime, a remote attestation solution, where strict type checking introduced in version 7.12.0 prevents the registrar from reading database entries created by previous versions, for example, 7.11.0. Specifically, older versions store agent registration data as bytes, whereas the updated registrar expects str. This issue leads to an exception when processing agent registration requests, causing the agent to fail.
- Record
EUVD-2025-4900- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Updated
- 2026-11-05
GitHub AdvisoriesGHSA-9jxq-5x44-gx23
4.3
Keylime registrar is vulnerable to Denial-of-Service attack when updated to version 7.12.0
Impact
The Keylime registrar implemented more strict type checking on version 7.12.0. As a result, when updated to version 7.12.0, the registrar will not accept the format of the data previously stored in the database by versions >= 7.8.0, raising an exception.
This makes the Keylime registrar vulnerable to a Denial-of-Service attack in an update scenario, as an attacker could populate the registrar database by creating multiple valid agent registrations with different UUIDs while the version is still < 7.12.0. Then, when the Keylime registrar is updated to the 7.12.0 version, any query to the database matching any of the entries populated by the attacker will result in failure.
Patches
Users should upgrade to versions >= 7.12.1
Workarounds
- Remove the registrar database and re-register all agents
Credit
Reported by: Anderson Toshiyuki Sasaki/@ansasaki Patched by: Anderson Toshiyuki Sasaki/@ansasaki
- Record
GHSA-9jxq-5x44-gx23- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-704, CWE-1287
- Updated
- 2026-11-02
NVD
4.3
A flaw was found in Keylime, a remote attestation solution, where strict type checking introduced in version 7.12.0 prevents the registrar from reading database entries created by previous versions, for example, 7.11.0. Specifically, older versions store agent registration data as bytes, whereas the updated registrar expects str. This issue leads to an exception when processing agent registration requests, causing the agent to fail.
- Record
CVE-2025-1057- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-704
- Updated
- 2026-11-05
OSV
4.3
Keylime: keylime registrar dos due to incompatible database entry handling
A flaw was found in Keylime, a remote attestation solution, where strict type checking introduced in version 7.12.0 prevents the registrar from reading database entries created by previous versions, for example, 7.11.0. Specifically, older versions store agent registration data as bytes, whereas the updated registrar expects str. This issue leads to an exception when processing agent registration requests, causing the agent to fail.
- Record
CVE-2025-1057- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-704
- Updated
- 2026-11-07
OSVGHSA-9jxq-5x44-gx23
4.3
Keylime registrar is vulnerable to Denial-of-Service attack when updated to version 7.12.0
Impact
The Keylime registrar implemented more strict type checking on version 7.12.0. As a result, when updated to version 7.12.0, the registrar will not accept the format of the data previously stored in the database by versions >= 7.8.0, raising an exception.
This makes the Keylime registrar vulnerable to a Denial-of-Service attack in an update scenario, as an attacker could populate the registrar database by creating multiple valid agent registrations with different UUIDs while the version is still < 7.12.0. Then, when the Keylime registrar is updated to the 7.12.0 version, any query to the database matching any of the entries populated by the attacker will result in failure.
Patches
Users should upgrade to versions >= 7.12.1
Workarounds
- Remove the registrar database and re-register all agents
Credit
Reported by: Anderson Toshiyuki Sasaki/@ansasaki Patched by: Anderson Toshiyuki Sasaki/@ansasaki
- Record
GHSA-9jxq-5x44-gx23- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Weakness
- CWE-1287, CWE-704
- Updated
- 2026-11-02
Show 4 moreShow less
OSVPYSEC-2026-1488
4.3
Keylime registrar is vulnerable to Denial-of-Service attack when updated to version 7.12.0
Impact
The Keylime registrar implemented more strict type checking on version 7.12.0. As a result, when updated to version 7.12.0, the registrar will not accept the format of the data previously stored in the database by versions >= 7.8.0, raising an exception.
This makes the Keylime registrar vulnerable to a Denial-of-Service attack in an update scenario, as an attacker could populate the registrar database by creating multiple valid agent registrations with different UUIDs while the version is still < 7.12.0. Then, when the Keylime registrar is updated to the 7.12.0 version, any query to the database matching any of the entries populated by the attacker will result in failure.
Patches
Users should upgrade to versions >= 7.12.1
Workarounds
- Remove the registrar database and re-register all agents
Credit
Reported by: Anderson Toshiyuki Sasaki/@ansasaki Patched by: Anderson Toshiyuki Sasaki/@ansasaki
- Record
PYSEC-2026-1488- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L - Updated
- 2026-11-02
OSVopenSUSE-SU-2025:14813-1 No score
keylime-config-7.12.1-1.1 on GA media
These are all security issues fixed in the keylime-config-7.12.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2025:14813-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2025:20159-1 No score
Security update for keylime
This update for keylime fixes the following issues:
Update to version 7.13.0+40.
Security issues fixed:
- CVE-2025-13609: possible agent identity takeover due to registrar allowing the registration of agents with duplicate UUIDs (bsc#1254199).
- CVE-2025-1057: registrar denial-of-service due to backward incompatibility in database type handling (bsc#1237153).
Other issues fixed and changes:
-
Version 7.13.0+40:
- Include new attestation information fields (#1818)
- Fix Database race conditions and SQLAlchemy 2.0 compatibility (#1823)
- push-model: require HTTPS for authentication and attestation endpoints
- Fix operational_state tracking in push mode attestations
- templates: add push model authentication config options to 2.5 templates
- Security: Hash authentication tokens in logs
- Fix stale IMA policy cache in verification
- Fix authentication behavior on failed attestations for push mode
- Add shared memory infrastructure for multiprocess communication
- Add agent authentication (challenge/response) protocol for push mode
- Add agent-driven (push) attestation protocol with PULL mode regression fixes (#1814)
- docs: Fix man page RST formatting for rst2man compatibility (#1813)
- Apply limit on keylime-policy workers
- tpm: fix ECC signature parsing to support variable-length coordinates
- tpm: fix ECC P-521 credential activation with consistent marshaling
- tpm: fix ECC P-521 coordinate validation
- Remove deprecated disabled_signing_algorithms configuration option (#1804)
- algorithms: add support for specific RSA algorithms
- algorithms: add support for specific ECC curve algorithms
- Created manpage for keylime-policy and edited manpages for keylime verifier, registrar, agent
- Manpage for keylime agent
- Manpage for keylime verifier
- Manpage for keylime registrar
- Use constants for timeout and max retries defaults
- verifier: Use timeout from
request_timeoutconfig option - revocation_notifier: Use timeout setting from config file
- tenant: Set timeout when getting version from agent
- verify/evidence: SEV-SNP evidence type/verifier
- verify/evidence: Add evidence type to request JSON
-
Version v7.13.0:
- Avoid re-encoding certificate stored in DB
- Revert "models: Do not re-encode certificate stored in DB"
- Revert "registrar_agent: Use pyasn1 to parse PEM"
- policy/sign: use print() when writing to /dev/stdout
- registrar_agent: Use pyasn1 to parse PEM
- models: Do not re-encode certificate stored in DB
- mba: normalize vendor_db in EV_EFI_VARIABLE_AUTHORITY events
- mb: support vendor_db as logged by newer shim versions
- mb: support EV_EFI_HANDOFF_TABLES events on PCR1
- Remove unnecessary configuration values
- cloud_verifier_tornado: handle exception in notify_error()
- requests_client: close the session at the end of the resource manager
- Manpage for keylime_tenant (#1786)
- Add 2.5 templates including Push Model changes
- Initial version of verify evidence API
- db: Do not read pool size and max overflow for sqlite
- Use context managers to close DB sessions
- revocations: Try to send notifications on shutdown
- verifier: Gracefully shutdown on signal
- Use
forkasmultiprocessingstart method - Fix inaccuracy in threat model and add reference to SBAT
- Explain TPM properties and expand vTPM discussion
- Fix invalid RST and update TOC
- Expand threat model page to include adversarial model
- Add --push-model option to avoid requests to agents
- templates: duplicate str_to_version() in the adjust script
- policy: fix mypy issues with rpm_repo
- revocation_notifier: fix mypy issue by replacing deprecated call
- Fix create_runtime_policy in python < 3.12
- Fix after review
- fixed CONSTANT names C0103 errors
- Extend meta_data field in verifierdb
- docs: update issue templates
- docs: add GitHub PR template with documentation reminders
- tpm_util: fix quote signature…
- Record
openSUSE-SU-2025:20159-1- Updated
- 2026-11-02
OSVSUSE-SU-2025:21194-1 No score
Security update for keylime
This update for keylime fixes the following issues:
Update to version 7.13.0+40.
Security issues fixed:
- CVE-2025-13609: possible agent identity takeover due to registrar allowing the registration of agents with duplicate UUIDs (bsc#1254199).
- CVE-2025-1057: registrar denial-of-service due to backward incompatibility in database type handling (bsc#1237153).
Other issues fixed and changes:
-
Version 7.13.0+40:
- Include new attestation information fields (#1818)
- Fix Database race conditions and SQLAlchemy 2.0 compatibility (#1823)
- push-model: require HTTPS for authentication and attestation endpoints
- Fix operational_state tracking in push mode attestations
- templates: add push model authentication config options to 2.5 templates
- Security: Hash authentication tokens in logs
- Fix stale IMA policy cache in verification
- Fix authentication behavior on failed attestations for push mode
- Add shared memory infrastructure for multiprocess communication
- Add agent authentication (challenge/response) protocol for push mode
- Add agent-driven (push) attestation protocol with PULL mode regression fixes (#1814)
- docs: Fix man page RST formatting for rst2man compatibility (#1813)
- Apply limit on keylime-policy workers
- tpm: fix ECC signature parsing to support variable-length coordinates
- tpm: fix ECC P-521 credential activation with consistent marshaling
- tpm: fix ECC P-521 coordinate validation
- Remove deprecated disabled_signing_algorithms configuration option (#1804)
- algorithms: add support for specific RSA algorithms
- algorithms: add support for specific ECC curve algorithms
- Created manpage for keylime-policy and edited manpages for keylime verifier, registrar, agent
- Manpage for keylime agent
- Manpage for keylime verifier
- Manpage for keylime registrar
- Use constants for timeout and max retries defaults
- verifier: Use timeout from
request_timeoutconfig option - revocation_notifier: Use timeout setting from config file
- tenant: Set timeout when getting version from agent
- verify/evidence: SEV-SNP evidence type/verifier
- verify/evidence: Add evidence type to request JSON
-
Version v7.13.0:
- Avoid re-encoding certificate stored in DB
- Revert "models: Do not re-encode certificate stored in DB"
- Revert "registrar_agent: Use pyasn1 to parse PEM"
- policy/sign: use print() when writing to /dev/stdout
- registrar_agent: Use pyasn1 to parse PEM
- models: Do not re-encode certificate stored in DB
- mba: normalize vendor_db in EV_EFI_VARIABLE_AUTHORITY events
- mb: support vendor_db as logged by newer shim versions
- mb: support EV_EFI_HANDOFF_TABLES events on PCR1
- Remove unnecessary configuration values
- cloud_verifier_tornado: handle exception in notify_error()
- requests_client: close the session at the end of the resource manager
- Manpage for keylime_tenant (#1786)
- Add 2.5 templates including Push Model changes
- Initial version of verify evidence API
- db: Do not read pool size and max overflow for sqlite
- Use context managers to close DB sessions
- revocations: Try to send notifications on shutdown
- verifier: Gracefully shutdown on signal
- Use
forkasmultiprocessingstart method - Fix inaccuracy in threat model and add reference to SBAT
- Explain TPM properties and expand vTPM discussion
- Fix invalid RST and update TOC
- Expand threat model page to include adversarial model
- Add --push-model option to avoid requests to agents
- templates: duplicate str_to_version() in the adjust script
- policy: fix mypy issues with rpm_repo
- revocation_notifier: fix mypy issue by replacing deprecated call
- Fix create_runtime_policy in python < 3.12
- Fix after review
- fixed CONSTANT names C0103 errors
- Extend meta_data field in verifierdb
- docs: update issue templates
- docs: add GitHub PR template with documentation reminders
- tpm_util: fix quote signature…
- Record
SUSE-SU-2025:21194-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
keylimePyPI |
7.12.0 to 7.12.0 | 7.12.1 |
keylimePyPI |
7.12.0 up to 7.12.1 | 7.12.1 |
keylimeSUSE:Linux Enterprise Server 16.0 From an advisory covering 2 CVEs |
before 7.13.0+40-160000.1.1 | 7.13.0+40-160000.1.1 |
keylimeSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 2 CVEs |
before 7.13.0+40-160000.1.1 | 7.13.0+40-160000.1.1 |
keylimeopenSUSE:Tumbleweed |
before 7.12.1-1.1 | 7.12.1-1.1 |
keylimeopenSUSE:Leap 16.0 From an advisory covering 2 CVEs |
before 7.13.0+40-160000.1.1 | 7.13.0+40-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | NVD, OSV | |
| facts | CVE List, EUVD | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2025-1057 is a medium vulnerability (CVSS 4.3) in Red Hat Enterprise Linux 10, published February 14, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.40%, the 34th percentile. Fixed in keylime 7.12.1.
References
access.redhat.com/security/cve/CVE-2025-1057
bugzilla.redhat.com/show_bug.cgi?id=2343894
github.com/ansasaki/keylime/tree/base64_bytes
github.com/keylime/rust-keylime
github.com/keylime/keylime/security/advisories/GHSA-9jxq-5x44-gx23
github.com/keylime/keylime/commit/e08b10d86c3717006774e787542c190e2ba24fc7
Show 12 moreShow less
nvd.nist.gov/vuln/detail/CVE-2025-1057
github.com/advisories/GHSA-9jxq-5x44-gx23
github.com/keylime/keylime
github.com/pypa/advisory-database/tree/main/vulns/keylime/PYSEC-2026-1488.yaml
pypi.org/project/keylime
access.redhat.com/downloads/content/package-browser
github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1057.json
suse.com/support/update/announcement/2025/suse-su-202521194-1
bugzilla.suse.com/1237153
bugzilla.suse.com/1254199
suse.com/security/cve/CVE-2025-1057
suse.com/security/cve/CVE-2025-13609
Left out here: the rest of 2 source descriptions. The JSON record has them.