← Back
CLEANSTART-2026-EI06494
Vulnerability in cert-manager-webhook-pdns-fips (CLEANSTART-2026-EI06494)
Summary
vulnerability in cert-manager-webhook-pdns-fips (CLEANSTART-2026-EI06494). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.2.3-r2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CLEANSTART-2026-EI06494** has been found in cert-manager-webhook-pdns-fips.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade cert-manager-webhook-pdns-fips to **3.2.3-r2** or later.
If unsure, ask your IT team or search "cert-manager-webhook-pdns-fips CLEANSTART-2026-EI06494" on the vendor's site.
CLEANSTART-2026-EI06494 (cert-manager-webhook-pdns-fips) —
Patched: `3.2.3-r2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in cert-manager-webhook-pdns-fips.
📍 Affected scope
cert-manager-webhook-pdns-fips — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.2.3-r2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'cert-manager-webhook-pdns-fips' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'cert-manager-webhook-pdns-fips' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `cert-manager-webhook-pdns-fips` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade cert-manager-webhook-pdns-fips to 3.2.3-r2ステージング環境で 3.2.3-r2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
CleanStart
cert-manager-webhook-pdns-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-r2"}]}]
References
- advisory https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-EI06494.json
- web https://osv.dev/vulnerability/CVE-2025-4673
- web https://osv.dev/vulnerability/CVE-2025-47907
- web https://osv.dev/vulnerability/CVE-2026-24051
- web https://osv.dev/vulnerability/CVE-2026-27143
- web https://osv.dev/vulnerability/CVE-2026-27144
- web https://osv.dev/vulnerability/CVE-2026-29181
- web https://osv.dev/vulnerability/CVE-2026-32280
- web https://osv.dev/vulnerability/CVE-2026-32281
- web https://osv.dev/vulnerability/CVE-2026-32282
- web https://osv.dev/vulnerability/CVE-2026-32283
- web https://osv.dev/vulnerability/CVE-2026-32289
- web https://osv.dev/vulnerability/CVE-2026-33186
- web https://osv.dev/vulnerability/CVE-2026-33810
- web https://osv.dev/vulnerability/CVE-2026-33811
- web https://osv.dev/vulnerability/CVE-2026-33814
- web https://osv.dev/vulnerability/CVE-2026-39817
- web https://osv.dev/vulnerability/CVE-2026-39819
- web https://osv.dev/vulnerability/CVE-2026-39820
- web https://osv.dev/vulnerability/CVE-2026-39823
- web https://osv.dev/vulnerability/CVE-2026-39825
- web https://osv.dev/vulnerability/CVE-2026-39826
- web https://osv.dev/vulnerability/CVE-2026-39836
- web https://osv.dev/vulnerability/CVE-2026-39883
- web https://osv.dev/vulnerability/CVE-2026-42499
- web https://osv.dev/vulnerability/CVE-2026-42501
- web https://osv.dev/vulnerability/ghsa-6vp2-p543-phr9
- web https://osv.dev/vulnerability/ghsa-9h8m-3fm2-qjrq
- web https://osv.dev/vulnerability/ghsa-cxp5-9wg8-vx66
- web https://osv.dev/vulnerability/ghsa-hcp3-c754-cr77
- web https://osv.dev/vulnerability/ghsa-hfvc-g4fc-pqhx
- web https://osv.dev/vulnerability/ghsa-mh2q-q3fh-2475
- web https://osv.dev/vulnerability/ghsa-p77j-4mvh-x3m3
- web https://osv.dev/vulnerability/ghsa-vugc-356p-c3xw
- web https://nvd.nist.gov/vuln/detail/CVE-2025-4673
- web https://nvd.nist.gov/vuln/detail/CVE-2025-47907
- web https://nvd.nist.gov/vuln/detail/CVE-2026-24051
- web https://nvd.nist.gov/vuln/detail/CVE-2026-27143
- web https://nvd.nist.gov/vuln/detail/CVE-2026-27144
- web https://nvd.nist.gov/vuln/detail/CVE-2026-29181
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32280
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32281
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32282
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32283
- web https://nvd.nist.gov/vuln/detail/CVE-2026-32289
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33186
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33810
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33811
- web https://nvd.nist.gov/vuln/detail/CVE-2026-33814
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39817
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39819
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39820
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39823
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39825
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39826
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39836
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39883
- web https://nvd.nist.gov/vuln/detail/CVE-2026-42499
- web https://nvd.nist.gov/vuln/detail/CVE-2026-42501