PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-55166 Netflix CVE debrief

Authenticated users in Lemur prior to 1.9.2 could manipulate ACME authority URLs to make backend requests, potentially exposing cloud credentials and private key material. The issue is fixed in version 1.9.2 with ACME_DIRECTORY_HOST_ALLOWLIST validation and enriched key-export audit events. This vulnerability allows attackers to target cloud instance metadata or internal services from the Lemur network context. The advisory also identifies creator-equality authorization behavior that could preserve access to certificate key material after ownership or role changes.

Vendor
Netflix
Product
lemur
CVSS
CRITICAL 9.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-18
Original CVE updated
2026-09-08
Advisory published
2026-08-18
Advisory updated
2026-09-08

Who should care

Defenders of Lemur deployments, cloud instance administrators, and teams responsible for certificate management and PKI should assess exposure and verify remediation. Affected operators must review compensating controls for exposed systems while remediation is scheduled and verified. Vulnerability management and security teams should prioritize updates to version 1.9.2 and monitor key export events for suspicious activity.

Why it matters

Authenticated users in Lemur prior to 1.9.2 could manipulate ACME authority URLs to make backend requests, potentially exposing cloud credentials and private key material. Defenders should verify remediation and assess exposure.

  • Potential exposure of cloud credentials
  • Potential exposure of long-lived PKI private-key access
  • Verification of creator-equality authorization behavior
  • Validation of ACME_DIRECTORY_HOST_ALLOWLIST implementation

Technical summary

The AcmeHandler.setup_acme_client in Lemur prior to 1.9.2 allows authenticated users to influence ACME authority acme_url without effective server-side destination restriction. This could trigger backend requests to cloud instance metadata or internal services, potentially obtaining credentials available to the host. The advisory also identifies creator-equality authorization behavior that could preserve access to certificate key material after ownership or role changes.

Defensive priority

High

Recommended defensive actions

  • Review and update Lemur to version 1.9.2 or later
  • Restrict ACME authority URLs to only allowlist of trusted hosts
  • Monitor and audit key export events for suspicious activity
  • Verify creator-equality authorization behavior and access controls
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The advisory describes a server-side request forgery and authorization weakness in Lemur's AcmeHandler.setup_acme_client. The fix adds validation and enriches audit events. Source grounding indicates that authenticated users could influence ACME authority URLs without effective server-side destination restriction. Evidence limits suggest verifying remediation and assessing exposure. Defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-55166 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-55166

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-55166 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-55166

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.