CVE-2026-70667

The record

Lemur manages TLS certificate creation. Prior to 1.9.3, _validate_revocation_url in lemur/certificates/verify.py checked the original CRL or OCSP URL but the later request could reach a different destination. The CRL requests.get call followed HTTP redirects without validating each Location target, so a public attacker-controlled URL could redirect to loopback, RFC1918, link-local, or instance-metadata addresses. Validation and connection also performed separate DNS resolutions, creating a time-of-check time-of-use window for DNS rebinding on both CRL and OCSP paths. An operator uploading a certificate through POST /api/1/certificates/upload could therefore induce blind internal requests despite the earlier mitigation. The fix disables redirects and pins validated addresses while preserving the correct Host value. This issue is fixed in version 1.9.3.

Affected packages

Related vulnerabilities

• CVE-2026-53613 util-linux is a random collection of Linux utilities. CWE-367
• CVE-2026-53612 util-linux is a random collection of Linux utilities. CWE-367
• CVE-2026-67693 An issue in gnutls v.3.8.13 allows an attacker to obtain sensitive information via… CWE-367
• CVE-2026-106451 yawkat LZ4 Java provides LZ4 compression for Java. CWE-367
• CVE-2026-86805 A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of… CWE-367
• CVE-2026-68488 A Time-of-check Time-of-use (TOCTOU) race condition leading to insecure symlink following… CWE-367
• CVE-2026-87554 Race condition in Chromoting in Google Chrome on on Windows prior to 153.0.8010.36… CWE-367
• CVE-2026-87523 Race condition in DataTransfer in Google Chrome prior to 153.0.8010.36 allowed a remote… CWE-367