🛡️ SUSE-SU-2026:0453-1 — rust-keylime (CVE-2026-25727)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for rust-keylime

This update for rust-keylime fixes the following issues:

Update to version 0.2.8+116.

Security issues fixed:

  • CVE-2026-25727: time: parsing of user-provided input by the RFC 2822 date parser can lead to stack exhaustion

(bsc#1257908).

Other updates and bugfixes:

  • Update vendored crates time to version 0.3.47.
  • Update to version 0.2.8+116:
  • build(deps): bump bytes from 1.7.2 to 1.11.1
  • api: Modify /version endpoint output in version 2.5
  • Add API v2.5 with backward-compatible /v2.5/quotes/integrity
  • tests: add unit test for resolve_agent_id (#1182)
  • (pull-model): enable retry logic for registration
  • rpm: Update specfiles to apply on master
  • workflows: Add test to detect unused crates
  • lib: Drop unused crates
  • push-model: Drop unused crates
  • keylime-agent: Drop unused crates
  • build(deps): bump uuid from 1.18.1 to 1.19.0
  • Update reqwest-retry to 0.8, retry-policies to 0.5
  • rpm: Fix cargo_build macro usage on CentOS Stream
  • fix(push-model): resolve hash_ek uuid to actual EK hash
  • build(deps): bump thiserror from 2.0.16 to 2.0.17
  • workflows: Separate upstream test suite from e2e coverage
  • Send UEFI measured boot logs as raw bytes (#1173)
  • auth: Add unit tests for SecretToken implementation
  • packit: Enable push-attestation tests
  • resilient_client: Prevent authentication token leakage in logs
  • Use tmpfiles.d for /var directories (PED-14736)
  • Update to version 0.2.8+96:
  • build(deps): bump wiremock from 0.6.4 to 0.6.5
  • build(deps): bump actions/checkout from 5 to 6
  • build(deps): bump chrono from 0.4.41 to 0.4.42
  • packit: Get coverage from Fedora 43 runs
  • Fix issues pointed out by clippy
  • Replace mutex unwraps with proper error handling in TPM library
  • Remove unused session request methods from StructureFiller
  • Fix config panic on missing ek_handle in push model agent
  • build(deps): bump tempfile from 3.21.0 to 3.23.0
  • build(deps): bump actions/upload-artifact from 4 to 6 (#1163)
  • Fix clippy warnings project-wide
  • Add KEYLIME_DIR support for verifier TLS certificates in push model agent
  • Thread privileged resources and use MeasurementList for IMA reading
  • Add privileged resource initialization and privilege dropping to push model agent
  • Fix privilege dropping order in run_as()
  • add documentation on FQDN hostnames
  • Remove confusing logs for push mode agent
  • Set correct default Verifier port (8891->8881) (#1159)
  • Add verifier_url to reference configuration file (#1158)
  • Add TLS support for Registrar communication (#1139)
  • Fix agent handling of 403 registration responses (#1154)
  • Add minor README.md rephrasing (#1151)
  • build(deps): bump actions/checkout from 5 to 6 (#1153)
  • ci: update spec files for packit COPR build
  • docs: improve challenge encoding and async TPM documentation
  • refactor: improve middleware and error handling
  • feat: add authentication client with middleware integration
  • docker: Include keylime_push_model_agent binary
  • Include attestation_interval configuration (#1146)
  • Persist payload keys to avoid attestation failure on restart
  • crypto: Implement the load or generate pattern for keys
  • Use simple algorithm specifiers in certification_keys object (#1140)
  • tests: Enable more tests in CI
  • Fix RSA2048 algorithm reporting in keylime agent
  • Remove disabled_signing_algorithms configuration
  • rpm: Fix metadata patches to apply to current code
  • workflows/rpm.yml: Use more strict patching
  • build(deps): bump uuid from 1.17.0 to 1.18.1
  • Fix ECC algorithm selection and reporting for keylime agent
  • Improve logging consistency and coherency
  • Implement minimal RFC compliance for Location header and URI parsing (#1125)
  • Use separate keys for payload mechanism and mTLS
  • docker: update rust to 1.81 for distroless Dockerfile
  • Ensure UEFI log capabilities are set to false
  • build(deps): bump http from 1.1.0 to 1.3.1
  • build(deps): bump log from 0.4.27 to 0.4.28
  • build(deps): bump cfg-if from 1.0.1 to 1.0.3
  • build(deps): bump actix-rt from 2.10.0 to 2.11.0
  • build(deps): bump async-trait from 0.1.88 to 0.1.89
  • build(deps): bump trybuild from 1.0.105 to 1.0.110
  • Accept evidence handling structures null entries
  • workflows: Add test to check if RPM patches still apply
  • CI: Enable test add-agent-with-malformed-ek-cert
  • config: Fix singleton tests
  • FSM: Remove needless lifetime annotations (#1105)
  • rpm: Do not remove wiremock which is now available in Fedora
  • Use latest Fedora httpdate version (1.0.3)
  • Enhance coverage with parse_retry_after test
  • Fix issues reported by CI regarding unwrap() calls
  • Reuse max retries indicated to the ResilientClient
  • Include limit of retries to 5 for Retry-After
  • Add policy to handle Retry-After response headers
  • build(deps): bump wiremock from 0.6.3 to 0.6.4
  • build(deps): bump serde_json from 1.0.

Affected software

SUSE-SU-2026:0453-1 is recorded against 1 package.

  • rust-keylime (fixed in 0.2.8+116-150400.3.13.1)

Timeline and source

Published on 11 February 2026 and last revised on 12 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

www.suse.com (Advisory)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-02-11
Updated 2026-08-20
Modified 2026-02-12
Fix URL N/A

Affected Packages

Software From version Fixed in
rust-keylime 0.2.8+116-150400.3.13.1

Free Vulnerability Check

Is your site affected by SUSE-SU-2026:0453-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-SU-2026:0453-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesSUSESUSE 2026