CVE-2023-26033

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Gentoo soko is the code that powers packages.gentoo.org. Versions prior to 1.0.1 are vulnerable to SQL Injection, leading to a Denial of Service. If the user selects (in user preferences) the "Recently Visited Packages" view for the index page, the value of the search_history cookie is used as a base64 encoded comma separated list of atoms. These are string loaded directly into the SQL query with atom = '%s' format string. As a result, any user can modify the browser's cookie value and inject most SQL queries. A proof of concept malformed cookie was generated that wiped the database or changed it's content. On the database, only public data is stored, so there is no confidentiality issues to site users. If it is known that the database was modified, a full restoration of data is possible by performing a full database wipe and performing full update of all components. This issue is patched with commit id 5ae9ca83b73. Version 1.0.1 contains the patch. If users are unable to upgrade immediately, the following workarounds may be applied: (1.) Use a proxy to always drop the search_history cookie until upgraded. The impact on user experience is low. (2.) Sanitize to the value of search_history cookie after base64 decoding it.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

February 25, 2023

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 29× 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 165 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-26033?
CVE-2023-26033 is a high vulnerability published on February 25, 2023. Gentoo soko is the code that powers packages.gentoo.org. Versions prior to 1.0.1 are vulnerable to SQL Injection, leading to a Denial of Service. If the user selects (in user preferences) the "Recently Visited Packages" view for the index page, the value of the searchhistory cookie is used as a…
When was CVE-2023-26033 disclosed?
CVE-2023-26033 was first published in the National Vulnerability Database on February 25, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-26033 actively exploited?
CVE-2023-26033 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.3% of all scored CVEs.
What is the CVSS score of CVE-2023-26033?
CVE-2023-26033 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-26033?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-26033, 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-2023-26033

Explore →

Is Your Infrastructure Affected by CVE-2023-26033?

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

Start Free Scan →Browse All CVEs