/

CVE-2026-71307

Severity:

HIGH RISK

(7.7)

Broken Access Control (CWE-862) in Lemur Destinations

CVE-2026-71307

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-862

Impact:

Unauthorized disclosure of credentials and access to external certificate-deployment systems

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Lemur destination read endpoints allowed authenticated users without the required administrative permission to retrieve destination configuration, including plaintext SFTP passwords and private-key passphrases. An attacker with read-only access could use those credentials to access remote certificate-deployment systems and TLS material outside Lemur's security boundary.

Affected context

The issue occurs in Lemur deployments where destination read handlers enforce authentication but do not apply the stronger authorization required by destination write handlers. Risk is increased when destination schemas expose raw plugin options and plugins store sensitive connection values, such as SFTP passwords or private-key passphrases, in retrievable form.

Exploit preconditions

  • Attack surface: Destination read API endpoints
  • Required access: Any authenticated account with permission to access the API; administrative permission was not consistently required
  • Trigger point: Retrieval of destination records through the affected read handlers
  • Why exploitation is possible: Read responses included unredacted plugin options, allowing sensitive destination credentials to be disclosed to users who were not authorized to view them

Why this happens

The underlying bug is an authorization gap in which authentication was treated as sufficient for reading destination resources, while comparable write operations required administrative authorization. The response schema also copied plugin options without applying sensitivity-aware redaction. This maps to CWE-862, Missing Authorization, because the application failed to enforce the necessary permission check for a protected read operation and thereby exposed confidential configuration data.

Potential impact

  • An attacker could obtain SFTP passwords or private-key passphrases.
  • Compromised credentials could permit unauthorized access to remote deployment hosts.
  • TLS certificates, keys, or related deployment material could be exposed or altered.
  • An attacker could use external system access for persistence, lateral movement, or service disruption.
  • Certificate deployment workflows could be manipulated or undermined.

General mitigation guidance

Mitigation generally centers on enforcing authorization consistently across

every operation and minimizing the sensitivity of returned configuration data.

Common defensive patterns include:

  • Require explicit administrative authorization for destination reads that expose protected configuration.
  • Apply field-level redaction to values marked sensitive before constructing API responses.
  • Avoid storing plaintext credentials in application configuration when managed secret references or a dedicated secret store are available.
  • Return only the minimum destination metadata needed by the requesting workflow.
  • Separate read access to operational metadata from access to connection secrets.
  • Apply least-privilege identities and narrowly scoped permissions to remote deployment systems.
  • Rotate credentials that may have been exposed and review access records for unusual retrieval activity.

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and authorization checks that compare read and write handler permission requirements.
  • Code review searches for authenticated-only endpoints returning secrets, plugin options, or configuration objects.
  • Schema and serializer reviews verifying that sensitive fields are consistently redacted.
  • API tests using low-privilege accounts to confirm that protected resources and fields are unavailable.
  • Policy enforcement requiring explicit authorization decorators or middleware on sensitive resource handlers.
  • Monitoring for unusual destination-listing activity and repeated access by read-only users.

Automated security review tools can help flag missing authorization checks and potential secret exposure, but endpoint-specific tests remain important.

Sources

SourceLink
github.comgithub.com/Netflix/lemur/commit/751c970ec42a53d00ecc9c6a96e0e51b6737ae53
github.comgithub.com/Netflix/lemur/releases/tag/v1.9.3
github.comgithub.com/Netflix/lemur/security/advisories/GHSA-6c8m-q6g9-vrw3

Frequently asked

questions

The described exposure requires authentication, but a user with only read-level

access may be able to retrieve sensitive destination values if authorization

is not enforced correctly.

Destination responses may include plugin options such as SFTP passwords and

private-key passphrases, depending on how the destination is configured.

Enforce administrator authorization for sensitive destination reads and redact

secret-bearing fields before responses are serialized. Prefer managed secret

references over returning or storing plaintext values.

Test every API operation with accounts at each privilege level, apply

field-level secrecy rules in schemas, use least privilege, and monitor access

to configuration endpoints and external deployment systems.

Find out what's already
exploitable in your codebase.