CVE-2026-81730

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Dolibarr 9.0.0 through 23.0.4 saves inbound email attachments under the name supplied in the message's MIME headers without reducing it to a safe basename. The global saveAttachment() in htdocs/emailcollector/lib/emailcollector.lib.php builds $filepath = $path . $filename . '.' . $ext and hands it to file_put_contents(), and the private saveAttachment() in htdocs/emailcollector/class/emailcollector.class.php writes to $destdir.'/'.$filename; the name reaches both from the attachment's own getName() or getFilename() value by way of the record-join, create-ticket and create-project operations. A traversal sequence in the filename therefore survives intact, so any sender who can email a mailbox that an EmailCollector monitors, which is the module's ordinary use for a support or ticket inbox, can place attacker-controlled content outside the per-object attachment directory without holding a Dolibarr account. Under the hardened layout Dolibarr's SECURITY.md requires, with htdocs read-only, the write is confined to the documents tree and corrupts or forges other objects' documents; where htdocs is writable the same primitive reaches a web-executable path. Version 24.0.0 applies dol_sanitizePathName() and dol_sanitizeFileName() before the write.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.6% × 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.6%
EPSS %ILE
45th
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

August 27, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
Patch available. Sources: github_commit.
Web page

Dolibarr 9.0.0 through 23.0.4 Path Traversal via EmailCollector Attachment Filename | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dolibarr-9.0.0-through-23.0.4-path-traversal-via-emailcollector-attachment-filename
Web page

dolibarr/htdocs/emailcollector/lib/emailcollector.lib.php at 23.0.4 · Dolibarr/dolibarr · GitHub

https://github.com/Dolibarr/dolibarr/blob/23.0.4/htdocs/emailcollector/lib/emailcollector.lib.php#L187
Web page

GitHub - Dolibarr/dolibarr: Dolibarr ERP CRM is a modern software package to manage your company or foundation's activity (contacts, suppliers, invoices, orders, stocks, agenda, accounting, ...). it's an open source Web application (written in PHP) designed for businesses of any sizes, foundations and freelancers. · GitHub

https://github.com/Dolibarr/dolibarr
GitHub commit Patch Available

commit 264a44defb5e (Dolibarr/dolibarr)

Patch available: Dolibarr/dolibarr 24.0.0 (contains commit 264a44defb5e)

https://github.com/Dolibarr/dolibarr/commit/264a44defb5e438689c75679617f6edc4c038abc

Vendor Advisories for CVE-2026-81730(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 107× 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 178 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 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81730?
CVE-2026-81730 is a high-severity vulnerability; its CVE record was published on August 27, 2026. Dolibarr 9.0.0 through 23.0.4 saves inbound email attachments under the name supplied in the message's MIME headers without reducing it to a safe basename. The global saveAttachment() in htdocs/emailcollector/lib/emailcollector.lib.php builds $filepath = $path . $filename . '.' . $ext and hands it…
When was CVE-2026-81730 made public?
CVE-2026-81730 was made public on July 7, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81730 actively exploited?
CVE-2026-81730 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81730?
CVE-2026-81730 has a CVSS base score of 8.2 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81730?
A fix for CVE-2026-81730 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81730 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81730?

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

Book a Demo →Browse All CVEs