CVE-2026-55443

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-16) is not newer than that change (2026-06-26), so it does not.

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

Also known asEUVD-2026-38332 (ENISA EUVD) · GHSA-gr75-jv2w-4656 (GitHub Security Advisories) · PYSEC-2026-2192 (OSV.dev) · PYSEC-2026-2556 (OSV.dev)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

LangChain is a framework for building agents and LLM-powered applications. Prior to 1.3.9, several LangChain components that resolve filesystem paths or expand search patterns do not consistently confine the resolved path to the intended root directory. Affected behaviors include: a file-search agent middleware that validates a starting directory but not the search pattern or the resolved target of matched files, so glob patterns and symlinks can reach files outside the configured root; prompt- and chain/agent-configuration loaders that accept path fields and resolve them without confining the result to a trusted base or rejecting symlink targets; and path-prefix authorization checks that compare by string prefix without a path-segment boundary, so a sibling path sharing the prefix is accepted. When these components receive path values, search patterns, or workspace contents influenced by an untrusted source — including an LLM acting on untrusted input — the result can be disclosure of files outside the intended boundary. This vulnerability is fixed in 1.3.9.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
11th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

June 22, 2026

Last Modified

June 26, 2026

Advisory Details (2)

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

Path traversal and sandbox escape in LangChain file-search middleware and loaders · Advisory · langchain-ai/langchain · GitHub

https://github.com/langchain-ai/langchain/security/advisories/GHSA-gr75-jv2w-4656
GitHub commit Patch Available

commit dcaf7795a3e6 (langchain-ai/langchain)

Patch available: langchain-ai/langchain langchain==1.3.9 (contains commit dcaf7795a3e6)

https://github.com/langchain-ai/langchain/commit/dcaf7795a3e6590af55c3ff7bda6add6355e9ea6

Vendor Advisories for CVE-2026-55443(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplangchain @ 1.3.9 (fixes <= 1.3.8)—ghsa
piplangchain-anthropic @ 1.4.6 (fixes <= 1.4.5)—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

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
langchain0.0.1 ... 1.3.8 (502 versions)
  • every version up to 1.3.9: fixed in 1.3.9
—
langchain-anthropic0.0.1 ... 1.4.5 (84 versions)
  • every version up to 1.4.6: fixed in 1.4.6
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-55443?
CVE-2026-55443 is a medium-severity vulnerability; its CVE record was published on June 22, 2026. LangChain is a framework for building agents and LLM-powered applications. Prior to 1.3.9, several LangChain components that resolve filesystem paths or expand search patterns do not consistently confine the resolved path to the intended root directory. Affected behaviors include: a file-search…
When was the CVE record for CVE-2026-55443 published?
The CVE record for CVE-2026-55443 was published on June 22, 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 June 26, 2026; the record at its source may have been updated since.
Is CVE-2026-55443 actively exploited?
CVE-2026-55443 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55443?
CVE-2026-55443 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-55443?
A fix for CVE-2026-55443 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55443 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-55443

Explore →

Is Your Infrastructure Affected by CVE-2026-55443?

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