CVE-2026-122244

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

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

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-11-20. A secondary CVSS source baseline 7.7; sources differ by 0.0.

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

Also known asEUVD-2026-131661 (ENISA EUVD) · GHSA-r2q3-7m4h-63qg (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Budibase is an open-source low-code platform. Prior to 3.50.0, a BASIC application user, or an unauthenticated visitor to a public write form, can store markup in a shared external datasource that a builder or administrator later evaluates in any Handlebars binding Preview that surfaces the value, including the Data-section Formula column editor or any binding drawer. jsonFormatter.format() in packages/frontend-core/src/utils/jsonFormatter.ts leaves raw strings and object keys unescaped, while packages/builder/src/components/common/bindings/EvaluationSidePanel.svelte inserts the formatted result as raw HTML. The Handlebars SafeString path preserves the attacker-controlled value, and the Builder origin lacks a Content-Security-Policy that would block the resulting script. This permits stored script execution in the higher-privileged builder or administrator session rather than the writer's own role, allowing privileged Builder API actions and workspace data access. This issue is fixed in versions 3.50.0 and 4.0.0.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
35
EG Risk 35/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.7%
EPSS %ILE
53rd
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 (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. 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: 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 or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

November 20, 2026

Last Modified

November 20, 2026

Advisory Details (4)

Auto-updated Nov 20, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v4.0.0

Patch available: Budibase/budibase v4.0.0

https://github.com/Budibase/budibase/releases/tag/v4.0.0
GitHub release Patch Available

v3.50.0

Patch available: Budibase/budibase v3.50.0

https://github.com/Budibase/budibase/releases/tag/v3.50.0
GitHub commit Patch Available

commit 5f37fb437286 (Budibase/budibase)

Patch available: Budibase/budibase v3.50.0 (contains commit 5f37fb437286)

https://github.com/Budibase/budibase/commit/5f37fb43728639c540cc7233283f1100e9315424
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Cross-privilege Stored XSS in the Budibase Builder via broken HTML-escaping in `jsonFormatter.format()` rendered through `{@html}` in the CSP-less Builder origin · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-r2q3-7m4h-63qg

Vendor Advisories for CVE-2026-122244(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@budibase/server—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-21 00:46 UTCEchelonGraph re-scored
  3. 2026-11-21 00:46 UTCGHSA enrichmentGHSA-r2q3-7m4h-63qg · GitHub severity HIGH · GitHub CVSS 7.7
  4. 2026-11-20 18:04 UTCENISA EUVD ID recordedEUVD-2026-131661 · Source: ENISA EUVD
  5. 2026-11-20 17:28 UTCEchelonGraph re-scored
  6. 2026-11-20 16:53 UTCEchelonGraph re-scoredFirst assessed: 7.7 HIGH
  7. 2026-11-20 16:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-122244?
CVE-2026-122244 is a high-severity vulnerability; its CVE record was published on November 20, 2026. Budibase is an open-source low-code platform. Prior to 3.50.0, a BASIC application user, or an unauthenticated visitor to a public write form, can store markup in a shared external datasource that a builder or administrator later evaluates in any Handlebars binding Preview that surfaces the value,…
When was the CVE record for CVE-2026-122244 published?
The CVE record for CVE-2026-122244 was published on November 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 November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-122244 actively exploited?
CVE-2026-122244 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-122244?
CVE-2026-122244 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-122244?
A fix for CVE-2026-122244 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-122244 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-122244?

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