{"items":[{"id":"NVI-00009103","kind":"vulnerability","title":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-8rvj-mm4h-c258","CVE-2026-62290"],"plain_summary":"GitHub lists this reviewed advisory for github.com/cert-manager/cert-manager, github.com/cert-manager/cert-manager. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-245c956b02e1490847046932142b2b8a"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:39:44.000Z","value":"7.3 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b2b22b101247055ff67f13e008d96cfb"},{"kind":"CVSS","as_of":"2026-07-30T14:27:48.843Z","value":"7.3 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-238da560f01baef73ba329ca9c68ac29"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.112%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.01362. Missing scores are unknown.","source_id":"sr-245c956b02e1490847046932142b2b8a"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b2b22b101247055ff67f13e008d96cfb","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-8rvj-mm4h-c258","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-238da560f01baef73ba329ca9c68ac29","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-62290","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T02:47:38.696Z"},{"id":"sr-245c956b02e1490847046932142b2b8a","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62290","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:45:16.075Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.18.0, < 1.19.6"]},{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.20.0-alpha.0, < 1.20.3"]}],"null_published_at":"2026-11-08T19:53:33.536Z","source_updated_at":"2026-10-29T16:39:44.000Z","source_disclosed_at":"2026-10-29T16:39:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00009103","kind":"vulnerability","title":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-8rvj-mm4h-c258","CVE-2026-62290"],"plain_summary":"GitHub lists this reviewed advisory for github.com/cert-manager/cert-manager, github.com/cert-manager/cert-manager. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1729d53f0e1baa8e2478adf091fb4ab0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:39:44.000Z","value":"7.3 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b2b22b101247055ff67f13e008d96cfb"},{"kind":"CVSS","as_of":"2026-07-30T14:27:48.843Z","value":"7.3 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-238da560f01baef73ba329ca9c68ac29"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.112%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.0135. Missing scores are unknown.","source_id":"sr-1729d53f0e1baa8e2478adf091fb4ab0"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b2b22b101247055ff67f13e008d96cfb","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-8rvj-mm4h-c258","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-238da560f01baef73ba329ca9c68ac29","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-62290","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T02:47:38.696Z"},{"id":"sr-1729d53f0e1baa8e2478adf091fb4ab0","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62290","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.18.0, < 1.19.6"]},{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.20.0-alpha.0, < 1.20.3"]}],"null_published_at":"2026-11-04T10:04:35.920Z","source_updated_at":"2026-10-29T16:39:44.000Z","source_disclosed_at":"2026-10-29T16:39:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00009103","kind":"vulnerability","title":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-8rvj-mm4h-c258","CVE-2026-62290"],"plain_summary":"GitHub lists this reviewed advisory for github.com/cert-manager/cert-manager, github.com/cert-manager/cert-manager. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1729d53f0e1baa8e2478adf091fb4ab0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:39:44.000Z","value":"7.3 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b2b22b101247055ff67f13e008d96cfb"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.112%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.0135. Missing scores are unknown.","source_id":"sr-1729d53f0e1baa8e2478adf091fb4ab0"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b2b22b101247055ff67f13e008d96cfb","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-8rvj-mm4h-c258","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-1729d53f0e1baa8e2478adf091fb4ab0","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-62290","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.18.0, < 1.19.6"]},{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.20.0-alpha.0, < 1.20.3"]}],"null_published_at":"2026-10-31T22:27:06.724Z","source_updated_at":"2026-10-29T16:39:44.000Z","source_disclosed_at":"2026-10-29T16:39:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00009103","kind":"vulnerability","title":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-8rvj-mm4h-c258","CVE-2026-62290"],"plain_summary":"GitHub lists this reviewed advisory for github.com/cert-manager/cert-manager, github.com/cert-manager/cert-manager. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-29T16:39:44.000Z","value":"7.3 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b2b22b101247055ff67f13e008d96cfb"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b2b22b101247055ff67f13e008d96cfb","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-8rvj-mm4h-c258","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.18.0, < 1.19.6"]},{"certainty":"source_listed","source_ids":["sr-b2b22b101247055ff67f13e008d96cfb"],"technology":"github.com/cert-manager/cert-manager","known_exclusions":[],"conditions_summary":"## Summary\n\n`Challenge` resources under `acme.cert-manager.io` can be created directly by namespace users. On create, cert-manager performs no admission validation tying the Challenge to an `Order`, an owner reference, or an Issuer-selected solver. The ACME Challenge controller then reconciles the direct resource and uses `Challenge.spec.solver` as the DNS01 provider configuration.\n\nWhen the direct Challenge references a `ClusterIssuer`, cert-manager derives the DNS provider secret namespace and ambient-credential policy from the `ClusterIssuer` reference, but the DNS provider configuration itself is attacker-controlled through `Challenge.spec.solver`. This lets a namespace user bypass `Issuer`/`ClusterIssuer` solver selectors such as `dnsZones`, `dnsNames`, and `matchLabels`, and make the cert-manager controller use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names.\n\nIn the acme-dns case, this becomes credential disclosure because the attacker-controlled solver host receives the `X-Api-User` and `X-Api-Key` headers loaded by cert-manager from the ClusterIssuer resource namespace.\n\n## Attack preconditions\n\n- The attacker can create `challenges.acme","public_affected_ranges":[">= 1.20.0-alpha.0, < 1.20.3"]}],"null_published_at":"2026-10-31T22:13:31.276Z","source_updated_at":"2026-10-29T16:39:44.000Z","source_disclosed_at":"2026-10-29T16:39:41.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:55:49.621Z"}],"next_cursor":null,"snapshot_revision":"42594"}