CVE-2026-62290Public exploit

DNS credential disclosure via unvalidated ACME Challenges

Published Jul 16, 2026 · Updated Jul 16, 2026

Incorrect authorization in cert-manager 1.18.0 through 1.19.5 and 1.20.0 through 1.20.2 allows local users to disclose acme-dns credentials. ValidateChallenge accepts a direct Challenge without tying it to an Order or Issuer-selected solver, so the controller trusts attacker-controlled provider settings and sends secret-backed X-Api-User and X-Api-Key headers to the selected host. Exploitation requires Challenge-create permission, a running cluster-wide controller, a usable ClusterIssuer, and DNS01 credentials; other providers expose policy bypass and unauthorized DNS mutation rather than demonstrated credential disclosure.

CVSS severity7.3
High
EPSS probability0.10%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in cert-manager 1.18.0 through 1.19.5 and 1.20.0 through 1.20.2 allows local users to disclose acme-dns credentials. ValidateChallenge accepts a direct Challenge without tying it to an Order or Issuer-selected solver, so the controller trusts attacker-controlled provider settings and sends secret-backed X-Api-User and X-Api-Key headers to the selected host. Exploitation requires Challenge-create permission, a running cluster-wide controller, a usable ClusterIssuer, and DNS01 credentials; other providers expose policy bypass and unauthorized DNS mutation rather than demonstrated credential disclosure.

The record

CVE
CVE-2026-62290
Published
Jul 16, 2026
Updated
Jul 16, 2026
Vendor
cert-manager
Product
cert-manager
Classifications
CWE-863, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 16, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.18.0, < 1.19.6
  2. Affected versionversion=>= 1.20.0, < 1.20.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

cert-manager · cert-managerversion=>= 1.18.0, < 1.19.6; version=>= 1.20.0, < 1.20.3

Published CVSS scores

7.3GitHubCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 11, 2026Sep 17, 2026
Latest reporting daySep 17, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization
T1068Exploitation for Privilege Escalation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo