p PatchFirst

CVE-2026-71417

CVE-2026-71417 · Lemur: Any user can revoke arbitrary certificates at the CA by uploading a duplicate record and revoking it

Esta página presenta datos de fuentes públicas de vulnerabilidades. Consulta el aviso original antes de actualizar.

Lemur manages TLS certificate creation. Prior to 1.9.3, POST /api/1/certificates/upload allowed a non-read-only user to create a duplicate row using another certificate body, authority_id, serial, or external_id without requiring permission on the underlying authority. PUT /api/1/certificates//revoke authorized the caller against only the selected Lemur row, so the creator of the duplicate bypassed CertificatePermission. The duplicate had no cert.endpoints, which also bypassed the safeguard that prevents revocation of deployed certificates. Issuer plugins then revoked the real CA-side certificate using certificate.body or external_id under the stored authority credentials. An attacker could therefore revoke arbitrary managed certificates and cause fleet-wide TLS denial of service. The fix rejects duplicate authority_id and serial identities, requires authority access on upload, and checks every matching row during revocation. This issue is fixed in version 1.9.3.

CVSS 7.3 · Alta · EPSS 0,1% · Corrección disponible

Publicación
Actualización

Pila tecnológica: python

Productos y versiones afectados

  • lemur

    Versiones
    • < 1.9.3: Afectada

    Sin corrección publicada

  • lemur PyPI

    Versiones
    • 0.11.0
    • 0.2.1
    • 0.8.0
    • 0.8.1
    • 0.9.0
    • 1.0.0
    • 1.1.0
    • 1.2.0
    • 1.3.1
    • 1.3.2
    • 1.4.0
    • 1.5.0
    • 1.6.0
    • 1.7.0
    • 1.8.0
    • 1.8.1
    • 1.8.2
    • 1.9.0
    • 1.9.1
    • 1.9.2
    Intervalos de versiones afectados
    • ECOSYSTEM: < 1.9.3

    Actualiza a 1.9.3

Fuentes originales

Comprueba tu servidor →