CVE-2026-18369

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.8 from GitHub Security Advisory published 2026-07-30. A secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity58% × 45%
The EG Score, 5.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available. Sources: redhat.
Red Hat

2509234 – (CVE-2026-18369) CVE-2026-18369 dogtag-pki: pki-core: redhat-pki: pki: ACME HTTP-01 validation SSRF via IP literal identifiers and unvalidated redirects

https://bugzilla.redhat.com/show_bug.cgi?id=2509234
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-18369

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatredhat-pki:10-8060020260814202723.07fb4edf2026-09-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dogtag-pki10.10.2-3 ... 11.2.1-2 (11 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 72× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 16:27 UTCEG score recompute
  4. 2026-10-11 20:07 UTCEG score recompute
  5. 2026-10-11 17:20 UTCEG score recompute
  6. 2026-10-11 14:52 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-06 23:54 UTCEG score recompute
  13. 2026-10-06 23:54 UTCVendor advisory
  14. 2026-10-06 23:54 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-05 20:01 UTCEG score recompute
  17. 2026-10-05 20:01 UTCVendor advisory
  18. 2026-10-05 20:01 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-04 06:41 UTCEG score recompute
  22. 2026-10-04 06:41 UTCVendor advisory
  23. 2026-10-04 06:41 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-02 17:00 UTCEG score recompute
Show 75 more
  1. 2026-10-02 16:59 UTCVendor advisory
  2. 2026-10-02 16:59 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  3. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-01 03:08 UTCEG score recompute
  5. 2026-10-01 03:08 UTCVendor advisory
  6. 2026-10-01 03:08 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  7. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-09-29 06:55 UTCEG score recompute
  10. 2026-09-29 06:55 UTCVendor advisory
  11. 2026-09-29 06:55 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  12. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-09-27 19:04 UTCEG score recompute
  14. 2026-09-27 19:04 UTCVendor advisory
  15. 2026-09-27 19:04 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  16. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-25 04:58 UTCEG score recompute
  19. 2026-09-25 04:58 UTCVendor advisory
  20. 2026-09-25 04:58 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  21. 2026-09-23 21:31 UTCEG score recompute
  22. 2026-09-23 21:31 UTCVendor advisory
  23. 2026-09-23 21:31 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  24. 2026-09-22 15:15 UTCEG score recompute
  25. 2026-09-22 15:15 UTCVendor advisory
  26. 2026-09-22 15:15 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  27. 2026-09-20 03:41 UTCEG score recompute
  28. 2026-09-20 03:41 UTCVendor advisory
  29. 2026-09-20 03:41 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  30. 2026-09-19 04:19 UTCEG score recompute
  31. 2026-09-19 04:19 UTCVendor advisory
  32. 2026-09-19 04:19 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  33. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-09-18 04:06 UTCEG score recompute
  35. 2026-09-18 04:06 UTCVendor advisory
  36. 2026-09-18 04:06 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  37. 2026-09-17 05:07 UTCEG score recompute
  38. 2026-09-17 05:07 UTCVendor advisory
  39. 2026-09-17 05:07 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  40. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-09-16 06:11 UTCEG score recompute
  42. 2026-09-16 06:11 UTCVendor advisory
  43. 2026-09-16 06:11 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  44. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-09-15 07:09 UTCEG score recompute
  46. 2026-09-15 07:09 UTCVendor advisory
  47. 2026-09-15 07:09 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  48. 2026-09-14 06:20 UTCEG score recompute
  49. 2026-09-14 06:20 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  50. 2026-09-14 05:40 UTCEG score recompute
  51. 2026-09-14 05:40 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  52. 2026-09-14 03:10 UTCEG score recompute
  53. 2026-09-14 03:10 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  54. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  55. 2026-09-13 04:14 UTCEG score recompute
  56. 2026-09-13 04:14 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  57. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-09-12 05:12 UTCEG score recompute
  59. 2026-09-12 05:12 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  60. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  61. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-09-11 06:15 UTCEG score recompute
  63. 2026-09-11 06:15 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  64. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-09-10 06:58 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  66. 2026-09-09 07:18 UTCEG score recompute
  67. 2026-09-09 07:18 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  68. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  69. 2026-09-07 20:03 UTCEG score recompute
  70. 2026-09-07 20:03 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  71. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  72. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  73. 2026-09-06 09:37 UTCEG score recompute
  74. 2026-09-06 09:37 UTCGHSA enrichmentGHSA-g3fm-cr7x-pwvj · GitHub CVSS 5.8
  75. 2026-09-05 10:41 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-18369?
CVE-2026-18369 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. 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…
When was CVE-2026-18369 made public?
CVE-2026-18369 was made public on July 30, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-18369 actively exploited?
CVE-2026-18369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18369?
CVE-2026-18369 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18369?
A fix for CVE-2026-18369 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18369 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18369

Explore →

Is Your Infrastructure Affected by CVE-2026-18369?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.