CVE-2026-71322

Lemur: Missing authorization check on POST /certificates/<id>/export for plugins with requires_key = False

In the current codebase:

• Any authenticated user can mint a Java truststore (java-truststore-jks plugin) containing any certificate's public body and chain, without owning the certificate or holding a role with permission over it.
• The audit log records a key_view event for the calling user against that certificate, despite no private key having been accessed. Defenders investigating apparent key-view events will encounter false positives that they cannot distinguish from genuine accesses.

Latent risk:

• A future ExportPlugin author who sets requires_key = False because their plugin can operate without a key (e.g., for a fall-back code path) but still uses the key when one is provided will silently leak private keys to any authenticated user. The same code review that approves the plugin will not flag this, the authorization invariant is held by a structurally distant if-branch in the view, not by the plugin itself.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-71322 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.9.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Lift the authorization check out of the if plugin.requires_key: block so it runs for every export call:

# Authorization first, unconditionally.
if g.current_user != cert.user:
    owner_role = role_service.get_by_name(cert.owner)
    permission = CertificatePermission(owner_role, [x.name for x in cert.roles])
    if not permission.can():
        return (dict(message="You are not authorized to export this certificate."), 403)
 
if plugin.requires_key:
    if not cert.private_key:
        return (dict(message="Plugin requires a key but none is present."), 400)
    log_service.create(g.current_user, "key_view", certificate=cert)   # only when key actually accessed
 
extension, passphrase, data = plugin.export(
    cert.body, cert.chain, cert.private_key, options
)

This makes the authorization gate independent of the plugin's requires_key flag and correctly scopes the key_view audit event to calls that actually involve key access.

1. What is CVE-2026-71322? CVE-2026-71322 is a medium-severity missing authorization vulnerability in lemur (pip), affecting versions < 1.9.3. It is fixed in 1.9.3. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-71322? CVE-2026-71322 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of lemur are affected by CVE-2026-71322? lemur (pip) versions < 1.9.3 is affected.
4. Is there a fix for CVE-2026-71322? Yes. CVE-2026-71322 is fixed in 1.9.3. Upgrade to this version or later.
5. Is CVE-2026-71322 exploitable, and should I be worried? Whether CVE-2026-71322 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-71322 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-71322? Upgrade lemur to 1.9.3 or later.

Other vulnerabilities in lemur