# CVE-2026-18369: Server-side request forgery in Red Hat Certificate System 10 > An unauthenticated attacker can exploit SSRF in the ACME HTTP-01 validator to access internal network services and potentially disclose response data. - **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Jul 2026 - **Updated:** 14 Sep 2026 - **Also known as:** DEBIAN-CVE-2026-18369, GHSA-g3fm-cr7x-pwvj, RHSA-2026:67110, UBUNTU-CVE-2026-18369 ## What is CVE-2026-18369? CVE-2026-18369 is a medium-severity server-side request forgery vulnerability in Red Hat Certificate System 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-18369? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `idm-console-framework` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:1.3.0-1.module+el8pki+14677+1ef79a68 | | `jss` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.11-1.module+el8pki+24697+be195eea | | `jss-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.11-1.module+el8pki+24697+be195eea | | `jss-debugsource` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.11-1.module+el8pki+24697+be195eea | | `jss-javadoc` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.9.11-1.module+el8pki+24697+be195eea | | `ldapjdk` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.23.0-1.module+el8pki+14677+1ef79a68 | | `ldapjdk-javadoc` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:4.23.0-1.module+el8pki+14677+1ef79a68 | | `python3-redhat-pki` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-acme` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-base` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-base-java` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-ca` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-console` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-console-theme` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-debugsource` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-est` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-javadoc` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-kra` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-ocsp` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-server` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-server-theme` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-symkey` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-symkey-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-tks` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-tools` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-tools-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-tps` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `redhat-pki-tps-debuginfo` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:10.13.14-1.module+el8pki+24697+be195eea | | `tomcatjss` | Red Hat:certificate_system_eus:10.4::el8 | All versions | 0:7.7.4-1.module+el8pki+21738+33a5e23b | ## How do I fix CVE-2026-18369? Apply the vendor's patch. ## Is CVE-2026-18369 being exploited? There is no known exploitation of CVE-2026-18369 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-18369 and fix it if it is affected. What it is: CVE-2026-18369 is a medium-severity server-side request forgery vulnerability in Red Hat Certificate System 10, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-18369 in the wild and no public exploit code. Affected product: Red Hat Certificate System 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-18369/ (Markdown: https://insights.sbomify.com/CVE-2026-18369/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18369 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18369 - OSV: https://osv.dev/vulnerability/CVE-2026-18369 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-18369/ Summaries are generated and may contain mistakes; the official description above is the record.