CVE-2026-114719

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.7 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-10-22) is not newer than that change (2026-11-02), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-107883 (ENISA EUVD) · GHSA-gmpp-w49q-937j (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
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: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a CSRF validation bypass in the mark-as-junk action of the markasjunk plugin. The plugin read the _uid parameter from POST data but passed it to rcmail::get_uids() without constraining the input mode, so values re-read inside that helper could be taken from the query string and the action carried out without a valid CSRF token. Upstream fixed this in the commit “Fix CSRF validation bypass in the mark-as-junk action”, which passes rcube_utils::INPUT_POST explicitly.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 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
12th
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 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-11-01). 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

October 22, 2026

Last Modified

November 2, 2026

Advisory Details (6)

Auto-updated Oct 30, 2026
Patch available. Sources: github_commit, github_release.
Web page

Security updates 1.6.20 and 1.7.5 released

https://roundcube.net/news/2026/10/19/security-updates-1.6.20-and-1.7.5
GitHub release Patch Available

Roundcube Webmail 1.7.5

Patch available: roundcube/roundcubemail 1.7.5

https://github.com/roundcube/roundcubemail/releases/tag/1.7.5
GitHub release Patch Available

Roundcube Webmail 1.6.20

Patch available: roundcube/roundcubemail 1.6.20

https://github.com/roundcube/roundcubemail/releases/tag/1.6.20
GitHub commit

commit 6ea2bbe35609 (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit 6ea2bbe35609 — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/6ea2bbe356099c9da98eabcfeafd8d6aa2d67b3d
GitHub commit

commit 15b0dc0d6e57 (roundcube/roundcubemail)

Fix landed in roundcube/roundcubemail commit 15b0dc0d6e57 — awaiting tagged release

https://github.com/roundcube/roundcubemail/commit/15b0dc0d6e5712310c8f663577361bf8132a7f81
Web pageMentions a patch (unverified)

#1151279 - roundcube: Multiple security vulnerabilities - Debian Bug report logs

https://bugs.debian.org/1151279

Vendor Advisories for CVE-2026-114719(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
roundcube1.6.1+dfsg-1 ... 1.6.9+dfsg-2 (39 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
roundcube1.6.11+dfsg-1 ... 1.6.19+dfsg-1 (16 versions)
  • every version up to 1.6.20+dfsg-0+deb13u1: fixed in 1.6.20+dfsg-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
roundcube1.6.11+dfsg-1 ... 1.6.19+dfsg-1 (9 versions)
  • every version up to 1.6.20+dfsg-1: fixed in 1.6.20+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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-13 16:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-11-02 16:28 UTCGHSA enrichmentGHSA-gmpp-w49q-937j · GitHub severity LOW · GitHub CVSS 3.7
  14. 2026-11-02 16:05 UTCEchelonGraph re-scored
  15. 2026-11-02 16:05 UTCGHSA enrichmentGHSA-gmpp-w49q-937j · GitHub severity LOW · GitHub CVSS 3.7
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  19. 2026-10-30 15:06 UTCEchelonGraph re-scored▲ 0.60
  20. 2026-10-30 15:06 UTCGHSA enrichmentGHSA-gmpp-w49q-937j · GitHub severity LOW · GitHub CVSS 3.7
  21. 2026-10-30 15:06 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  22. 2026-10-30 03:25 UTCOSV refresh
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  24. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  25. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
Show 11 more
  1. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-10-25 14:50 UTCEchelonGraph re-scored
  4. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-10-22 17:13 UTCEchelonGraph re-scored
  7. 2026-10-22 17:13 UTCGHSA enrichmentGHSA-gmpp-w49q-937j · GitHub severity LOW · GitHub CVSS 3.7
  8. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-10-22 02:26 UTCEchelonGraph re-scored
  10. 2026-10-22 01:36 UTCEchelonGraph re-scoredFirst assessed: 3.7 LOW
  11. 2026-10-22 01:35 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-114719?
CVE-2026-114719 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a CSRF validation bypass in the mark-as-junk action of the markasjunk plugin. The plugin read the _uid parameter from POST data but passed it to rcmail::get_uids() without constraining the input mode, so values re-read inside…
When was the CVE record for CVE-2026-114719 published?
The CVE record for CVE-2026-114719 was published on October 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 November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-114719 actively exploited?
CVE-2026-114719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114719?
CVE-2026-114719 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-114719?
A fix for CVE-2026-114719 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114719 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-114719

Explore →

Is Your Infrastructure Affected by CVE-2026-114719?

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

Book a Demo →Browse All CVEs