CVE-2026-90771

LOWPre-NVD 3.73.7
EchelonGraph scoreMEDIUM confidence

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

Score 3.7 from GitHub Security Advisory published 2026-09-13. A secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-76992 (ENISA EUVD) · GHSA-wr44-6hxh-3jwq (GitHub Security Advisories)Source: ENISA EUVD

3.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 3.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

joi before versions 17.13.8 and 18.2.9 contains a prototype pollution vulnerability in the messages compilation function that accepts __proto__ as an error code. Attackers can supply __proto__ keys in custom messages to replace the returned object's prototype, breaking downstream code relying on Object.prototype methods.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/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)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.4%
EPSS %ILE
33rd
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 (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

September 13, 2026

Last Modified

September 24, 2026

References (5)

Vendor Advisories for CVE-2026-90771(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana13-1-main-13.1.3-0.9.hum12026-09-15redhat
redhatgrafana13-2-main-13.2.1-0.4.hum12026-09-15redhat
redhatgrafana12-4-main-12.4.10-0.3.hum12026-09-15redhat

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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
joi—
  • every version up to 17.13.8: fixed in 17.13.8
  • 18.0.0 up to 18.2.9: fixed in 18.2.9
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× 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.

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. 1 repeat row among the latest 85 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-27 11:25 UTCOSV refresh
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-25 13:51 UTCEG score recompute
  11. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-18 03:00 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-13 12:34 UTCEG score recompute
  25. 2026-10-13 12:34 UTCVendor advisory
Show 59 more
  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-12 14:46 UTCEG score recompute
  3. 2026-10-11 19:14 UTCEG score recompute
  4. 2026-10-11 16:30 UTCEG score recompute
  5. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-11 13:45 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-10 18:56 UTCEG score recompute
  9. 2026-10-10 18:56 UTCVendor advisory
  10. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-07 14:38 UTCEG score recompute
  14. 2026-10-07 14:38 UTCVendor advisory
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-04 09:50 UTCEG score recompute
  19. 2026-10-04 09:50 UTCVendor advisory
  20. 2026-10-04 09:50 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  21. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-01 05:28 UTCEG score recompute
  23. 2026-10-01 05:28 UTCVendor advisory
  24. 2026-10-01 05:28 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  25. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-09-28 01:12 UTCEG score recompute
  28. 2026-09-28 01:12 UTCVendor advisory
  29. 2026-09-28 01:12 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  30. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-09-24 20:56 UTCEG score recompute
  33. 2026-09-24 20:56 UTCVendor advisory
  34. 2026-09-24 20:56 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  35. 2026-09-24 14:53 UTCEG score recompute
  36. 2026-09-24 14:53 UTCVendor advisory
  37. 2026-09-24 14:53 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-09-23 00:02 UTCEG score recompute
  41. 2026-09-23 00:02 UTCVendor advisory
  42. 2026-09-23 00:02 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  43. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-09-19 19:46 UTCEG score recompute
  47. 2026-09-19 19:46 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  48. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-09-16 15:30 UTCEG score recompute
  51. 2026-09-16 15:30 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  52. 2026-09-16 14:26 UTCEG score recompute
  53. 2026-09-16 14:26 UTCGHSA enrichmentGHSA-wr44-6hxh-3jwq · GitHub CVSS 3.7
  54. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-09-13 11:21 UTCEG score recompute
  58. 2026-09-13 10:50 UTCEG score recomputeFirst assessed: 3.7 LOW
  59. 2026-09-13 10:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-90771?
CVE-2026-90771 is a low-severity vulnerability; its CVE record was published on September 13, 2026. joi before versions 17.13.8 and 18.2.9 contains a prototype pollution vulnerability in the messages compilation function that accepts proto as an error code. Attackers can supply proto keys in custom messages to replace the returned object's prototype, breaking downstream code relying on…
When was CVE-2026-90771 made public?
CVE-2026-90771 was made public on September 9, 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 September 13, 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-90771 actively exploited?
CVE-2026-90771 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90771?
CVE-2026-90771 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90771?
A fix for CVE-2026-90771 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90771 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-90771

Explore →

Is Your Infrastructure Affected by CVE-2026-90771?

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

Book a Demo →Browse All CVEs