CVE-2026-63011

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-121330 (ENISA EUVD)Source: ENISA EUVD

9.4EG
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.3%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.167, 25.0.102, and 26.0.27, the Contact/labels JMAP endpoint in GroupOffice accepts a fully attacker-controlled template string (tpl parameter) that is passed without restriction to TemplateParser::parse(). When the template contains an [assign] block whose expression includes a {{...}} variable reference, the engine calls eval() on the expanded expression after running it through a validateExpression() guard. The guard double-quotes unrecognized tokens, but PHP 7+ allows a string enclosed in parentheses to be invoked as a function ("system")("id") is valid PHP and calls system("id"). A single authenticated HTTP request is sufficient to execute arbitrary OS commands as the web server user (www-data). This issue has been patched in versions 6.8.167, 25.0.102, and 26.0.27.

CVSS
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 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.
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 none (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.
EPSS PROB
0.3%
EPSS %ILE
28th
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 (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 (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

November 10, 2026

Last Modified

November 12, 2026

Advisory Details (4)

Auto-updated Nov 10, 2026
Patch available. Sources: github, github_release.
GitHub release Patch Available

v6.8.167

Patch available: Intermesh/groupoffice v6.8.167

https://github.com/Intermesh/groupoffice/releases/tag/v6.8.167
GitHub release Patch Available

v26.0.27

Patch available: Intermesh/groupoffice v26.0.27

https://github.com/Intermesh/groupoffice/releases/tag/v26.0.27
GitHub release Patch Available

v25.0.102

Patch available: Intermesh/groupoffice v25.0.102

https://github.com/Intermesh/groupoffice/releases/tag/v25.0.102
GitHub advisoryMentions a patch (unverified)

RCE - GroupOffice TemplateParser eval() via Contact/labels · Advisory · Intermesh/groupoffice · GitHub

https://github.com/Intermesh/groupoffice/security/advisories/GHSA-4m9w-3p93-6cwx

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 → 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-12 22:28 UTCEchelonGraph re-scored
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-11-12 02:20 UTCEchelonGraph re-scored
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  5. 2026-11-10 21:27 UTCEchelonGraph re-scored
  6. 2026-11-10 21:15 UTCEchelonGraph re-scored
  7. 2026-11-10 17:27 UTCEchelonGraph re-scored
  8. 2026-11-10 17:00 UTCENISA EUVD ID recordedEUVD-2026-121330 · Source: ENISA EUVD
  9. 2026-11-10 16:46 UTCEchelonGraph re-scoredFirst assessed: 9.4 CRITICAL
  10. 2026-11-10 16:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63011?
CVE-2026-63011 is a critical-severity vulnerability; its CVE record was published on November 10, 2026. Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.167, 25.0.102, and 26.0.27, the Contact/labels JMAP endpoint in GroupOffice accepts a fully attacker-controlled template string (tpl parameter) that is passed without restriction to…
When was the CVE record for CVE-2026-63011 published?
The CVE record for CVE-2026-63011 was published on November 10, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-63011 actively exploited?
CVE-2026-63011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63011?
CVE-2026-63011 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63011?
A fix for CVE-2026-63011 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63011?

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

Book a Demo →Browse All CVEs