CVE-2026-1709 — Keylime Registrar TLS Client Authentication Bypass (CVE-2026-1709)

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Keylime Keylime, Red Hat Enterprise Linux, Red Hat Enterprise Linux Eus…).
2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. EPSS ahead of 93% of scored CVEs: prioritize it in the patch queue.
5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-322

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 5.79%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

Analysis and videos

CVE-2026-1709: Keylime Registrar TLS Client Authentication Bypass
CVE-2026-1709 is a critical authentication bypass in the Keylime registrar, which the record says does not enforce client-side TLS authentication. According to the record, an unauthenticated client with network access could perform administrative operations such as listing agents, retrieving public TPM data and deleting agents. The sources consulted show no confirmed exploitation, and the record lists no fixed version.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · red hat/red hat enterprise linux 10, red hat/red hat enterprise linux 10.0 extended update support, red hat/red hat ente
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 9.8
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Modified
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• CVE published
  Feb 6, 2026 · redhat

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

6 on the record

• access.redhat.com/errata/RHSA-2026:2298
  Third Party Advisory, vendor-advisory, x_refsource_REDHAT, NIST National Vulnerability Database
• access.redhat.com/errata/RHSA-2026:2224
  Third Party Advisory, vendor-advisory, x_refsource_REDHAT, NIST National Vulnerability Database
• bugzilla.redhat.com/show_bug.cgi
  Issue Tracking, Third Party Advisory, issue-tracking, x_refsource_REDHAT, NIST National Vulnerability Database
• security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1709.json
  NIST National Vulnerability Database
• access.redhat.com/errata/RHSA-2026:2225
  Third Party Advisory, vendor-advisory, x_refsource_REDHAT, NIST National Vulnerability Database
• access.redhat.com/security/cve/CVE-2026-1709
  Third Party Advisory, vdb-entry, x_refsource_REDHAT, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2026-110924 Openssh: openssh: gssapi delegated credentials can be stored after a failed authentication 5h
• Medium CVE-2026-110927 Openssh: openssh: a compressed payload can expand past the maximum packet size 5h
• Medium CVE-2026-110926 Openssh: openssh: shared lz77 compression dictionary leaks plaintext across channels 13h
• Medium CVE-2026-110925 Openssh: openssh: '$' and '\' in a command-line username expand through %u 13h
• Medium CVE-2026-110923 Openssh: openssh: sftp can write outside the destination directory from a server-supplied path 13h
• High CVE-2026-86848 Dpdk: dpdk: time-of-check/time-of-use vulnerability allowing guest-triggered out-of-bounds write in vhost-crypto 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-1709 is "Keylime Registrar TLS Client Authentication Bypass (CVE-2026-1709)", rated Critical. It affects Keylime (Keylime); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 5.79% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.