SSRF (Server-Side Request Forgery) in Dogtag PKI's ACME responder (CVE-2026-18369)
Summary
SSRF in Dogtag PKI's ACME responder (CVE-2026-18369). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A flaw was found in Dogtag PKI's ACME responder where the HTTP-01 challenge validator accepts IP address literals as dns identifiers and follows HTTP redirects without validating that the target is a public address. An unauthenticated ACME account holder can exploit this to perform server-side request forgery (SSRF), making the Dogtag server send HTTP GET requests to internal network services. With the InMemory database backend, the response body of internal targets is disclosed to the attacker through the ACME challenge error.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-18369 has been found in Dogtag PKI's ACME responder.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Dogtag PKI's ACME responder CVE-2026-18369" on the vendor's site.
CVE-2026-18369 (Dogtag PKI's ACME responder) — CWE-918 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
SSRF (CWE-918) exists in Dogtag PKI's ACME responder.
Check the vendor advisory for the affected versions of Dogtag PKI's ACME responder.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Dogtag PKI's ACME responder を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-18369 dogtag-pki
- Ubuntu UBUNTU-CVE-2026-18369 dogtag-pki
References
- web nvd.nist.gov
- web access.redhat.com
- web bugzilla.redhat.com
- web github.com
- web access.redhat.com