CVE-2026-28684

MEDIUMNVD 6.66.6
EchelonGraph scoreMEDIUM confidence

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

Score 6.6 from GitHub Security Advisory (severity: MODERATE) published 2026-04-21. NVD baseline CVSS 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-23901 (ENISA EUVD) · GHSA-mf9w-mj56-hr94 (GitHub Security Advisories)Source: ENISA EUVD

6.6EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

python-dotenv reads key-value pairs from a .env file and can set them as environment variables. Prior to version 1.2.2, set_key() and unset_key() in python-dotenv follow symbolic links when rewriting .env files, allowing a local attacker to overwrite arbitrary files via a crafted symlink when a cross-device rename fallback is triggered. Users should upgrade to v.1.2.2 or, as a workaround, apply the patch manually.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity66% × 45%
Impact severity (EG Severity): CVSS 6.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
16th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.6): severity, escalated by confirmed exploitation. This CVE's 6.6 is its impact severity (EG Severity), not escalated.

EG Severity
6.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

April 20, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Jun 14, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Symlink following in set_key allows arbitrary file overwrite via cross-device rename fallback · Advisory · theskumar/python-dotenv · GitHub

https://github.com/theskumar/python-dotenv/security/advisories/GHSA-mf9w-mj56-hr94
GitHub release Patch Available

v1.2.2

Patch available: theskumar/python-dotenv v1.2.2

https://github.com/theskumar/python-dotenv/releases/tag/v1.2.2
GitHub commit Patch Available

commit 790c5c029911 (theskumar/python-dotenv)

Patch available: theskumar/python-dotenv v1.2.2 (contains commit 790c5c029911)

https://github.com/theskumar/python-dotenv/commit/790c5c02991100aa1bf41ee5330aca75edc51311

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-caikit-nlp-rhel9:17914482122026-10-21redhat
redhatrhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9:17900774882026-09-30redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatrhoai/odh-llama-stack-core-rhel9:17837015982026-07-21redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17824716062026-07-09redhat
redhatsatellite/iop-host-inventory-rhel9:17804142372026-06-16redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17797728772026-06-09redhat
redhatrhoai/odh-vllm-gaudi-rhel9:17786001872026-05-20redhat
pippython-dotenv @ 1.2.2 (fixes < 1.2.2)—ghsa

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-dotenv0.15.0-1 ... 1.2.1-2 (9 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-dotenv0.21.0-1, 1.0.0-1, 1.0.1-1, 1.2.1-1, 1.2.1-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-dotenv1.0.1-1, 1.2.1-1, 1.2.1-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-dotenv1.0.1-1, 1.2.1-1, 1.2.1-2
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
python-dotenv0.1.0 ... 1.2.1 (49 versions)
  • every version up to 1.2.2: fixed in 1.2.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 43× 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 95 of 239 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-28684?
CVE-2026-28684 is a medium-severity vulnerability; its CVE record was published on April 20, 2026. python-dotenv reads key-value pairs from a .env file and can set them as environment variables. Prior to version 1.2.2, set_key() and unset_key() in python-dotenv follow symbolic links when rewriting .env files, allowing a local attacker to overwrite arbitrary files via a crafted symlink when a…
When was the CVE record for CVE-2026-28684 published?
The CVE record for CVE-2026-28684 was published on April 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-28684 actively exploited?
CVE-2026-28684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28684?
CVE-2026-28684 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-28684?
A fix for CVE-2026-28684 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-28684 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-28684

Explore →

Is Your Infrastructure Affected by CVE-2026-28684?

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