CVE-2026-44843

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
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.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.85 and 1.3.3, LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call load() with allowed_objects="all". This does not enable arbitrary Python object deserialization, but it does allow any trusted LangChain-serializable object to be revived, which is broader than these runtime paths require. As a result, attacker-supplied LangChain serialized constructor dictionaries may cause trusted runtime paths to instantiate classes with untrusted constructor arguments. This vulnerability is fixed in 0.3.85 and 1.3.3.

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 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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
30th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

May 26, 2026

Last Modified

July 24, 2026

Advisory Details (1)

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

Unsafe deserialization of attacker-controlled LangChain objects through overly broad `load()` allowlists · Advisory · langchain-ai/langchain · GitHub

https://github.com/langchain-ai/langchain/security/advisories/GHSA-pjwx-r37v-7724

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17895706742026-09-30redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17873305852026-08-27redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
langchain-core0.0.1 ... 1.3.2 (266 versions)
  • 1.0.0 up to 1.3.3: fixed in 1.3.3
  • every version up to 0.3.85: fixed in 0.3.85
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-44843?
CVE-2026-44843 is a high-severity vulnerability; its CVE record was published on May 26, 2026. LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.85 and 1.3.3, LangChain contains older runtime code paths that deserialize run inputs, run outputs, or other application-controlled payloads using overly broad object allowlists. These paths may call load() with…
When was the CVE record for CVE-2026-44843 published?
The CVE record for CVE-2026-44843 was published on May 26, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-44843 actively exploited?
CVE-2026-44843 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44843?
CVE-2026-44843 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-44843?
A fix for CVE-2026-44843 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44843 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-44843

Explore →

Is Your Infrastructure Affected by CVE-2026-44843?

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