CVE-2026-46446

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

SOGo before 5.12.7, when PostgreSQL or MariaDB is used, and cleartext passwords are stored, allows SQL injection. This is related to c_password = '%@' in changePasswordForLogin.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 14, 2026

Advisory Details (3)

Auto-updated May 14, 2026
No patch confirmed yet.
generic

SOGo v5.12.7 released

https://www.sogo.nu/news/2026/sogo-v5127-released.html
generic

Bug#1136070: trixie-pu: package sogo/5.12.1-3+deb13u2

https://www.mail-archive.com/debian-bugs-dist%40lists.debian.org/msg2100131.html
generic

fix(sql): use proper sql adaptor for usr source by tkeriven · Pull Request #379 · Alinto/sogo · GitHub

https://github.com/Alinto/sogo/pull/379/changes/1f7e5d2b2c2047c44a6a9e05f73c36491cb96d21

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusogo-common (2.2.17a-1.1ubuntu0.1~esm1) @ xenial2026-08-23ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
sogo5.0.1-4 ... 5.9.1-1 (48 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
sogo5.8.0-1, 5.8.0-2+deb12u1, 5.8.0-2+deb12u25.8.0-2+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sogo5.12.1-3, 5.12.1-3+deb13u15.12.1-3+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sogo5.12.1-3 ... 5.12.6-1 (7 versions)5.12.7-1—

Weakness Classification(1)

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 7× in last 7d / 37× 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 241 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46446?
CVE-2026-46446 is a high vulnerability published on May 14, 2026. SOGo before 5.12.7, when PostgreSQL or MariaDB is used, and cleartext passwords are stored, allows SQL injection. This is related to c_password = '%@' in changePasswordForLogin.
When was CVE-2026-46446 disclosed?
CVE-2026-46446 was first published in the National Vulnerability Database on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46446 actively exploited?
CVE-2026-46446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46446?
CVE-2026-46446 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46446, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46446?

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

Start Free Scan →Browse All CVEs