CVE-2026-27851

CRITICALNVD 9.17.4
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-05-12. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

A fix is available — apply it.

When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to be unescaped. This can enable SQL / LDAP injection attacks when used in authentication. Avoid using safe filter until on fixed version. No publicly available exploits are known.

CVSS v3
9.1
EG Score
7.4(medium)
EPSS
33.1%
KEV
Not listed

Published

May 12, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 18, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-27851(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudovecot-submissiond (1:2.4.2+dfsg1-3ubuntu2.1) @ resolute2026-06-28ubuntu

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.

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 184 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 02:19 UTCOSV refresh
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 02:25 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  21. 2026-07-13 22:30 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-10 12:26 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  2. 2026-07-10 12:12 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 04:33 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 02:25 UTCVendor advisory
  24. 2026-06-28 02:25 UTCGHSA enrichment
  25. 2026-06-27 09:31 UTCVendor advisory
  26. 2026-06-27 09:31 UTCGHSA enrichment
  27. 2026-06-27 03:08 UTCEPSS rescore
  28. 2026-06-26 20:57 UTCVendor advisory
  29. 2026-06-26 20:56 UTCGHSA enrichment
  30. 2026-06-25 23:28 UTCVendor advisory
  31. 2026-06-25 23:27 UTCGHSA enrichment
  32. 2026-06-25 13:49 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-24 14:05 UTCEPSS rescore
  35. 2026-06-24 14:05 UTCEPSS rescore
  36. 2026-06-23 21:33 UTCEPSS rescore
  37. 2026-06-23 21:32 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 14:56 UTCEPSS rescore
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-19 19:25 UTCEPSS rescore
  45. 2026-06-19 19:25 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-17 17:53 UTCEPSS rescore
  48. 2026-06-17 17:53 UTCEPSS rescore
  49. 2026-06-17 00:35 UTCVendor advisory
  50. 2026-06-17 00:35 UTCGHSA enrichment
  51. 2026-06-16 17:52 UTCEPSS rescore
  52. 2026-06-16 06:50 UTCVendor advisory
  53. 2026-06-16 06:49 UTCGHSA enrichment
  54. 2026-06-15 17:48 UTCEPSS rescore
  55. 2026-06-15 01:42 UTCVendor advisory
  56. 2026-06-15 01:42 UTCGHSA enrichment
  57. 2026-06-14 23:18 UTCEPSS rescore
  58. 2026-06-14 13:27 UTCVendor advisory
  59. 2026-06-14 13:27 UTCGHSA enrichment
  60. 2026-06-14 01:05 UTCVendor advisory
  61. 2026-06-14 01:05 UTCGHSA enrichment
  62. 2026-06-13 23:00 UTCEPSS rescore
  63. 2026-06-13 01:04 UTCVendor advisory
  64. 2026-06-13 01:04 UTCGHSA enrichment
  65. 2026-06-13 00:57 UTCGHSA enrichment
  66. 2026-06-12 23:12 UTCEPSS rescore
  67. 2026-06-12 23:12 UTCEPSS rescore
  68. 2026-06-12 12:41 UTCVendor advisory
  69. 2026-06-12 12:41 UTCGHSA enrichment
  70. 2026-06-12 00:27 UTCVendor advisory
  71. 2026-06-12 00:27 UTCGHSA enrichment
  72. 2026-06-11 14:00 UTCEPSS rescore
  73. 2026-06-11 12:12 UTCVendor advisory
  74. 2026-06-11 12:12 UTCGHSA enrichment
  75. 2026-06-10 23:55 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-27851?
CVE-2026-27851 is a critical vulnerability published on May 12, 2026. When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to be unescaped. This can enable SQL / LDAP injection attacks when used in authentication. Avoid using safe filter until on fixed version. No…
When was CVE-2026-27851 disclosed?
CVE-2026-27851 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27851 actively exploited?
CVE-2026-27851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-27851?
CVE-2026-27851 has a CVSS v3 base score of 9.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
How do I remediate CVE-2026-27851?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27851, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27851

Explore →

Is Your Infrastructure Affected by CVE-2026-27851?

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