CVE-2026-104140

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (15th 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
Elevated

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

6.1EG
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.2%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

QGIS is a free, open source, cross-platform geographic information system. Prior to 3.44.12 and 4.0.0 through 4.2.3, QGIS Server renders feature data in WFS3 (OGC API Features) HTML responses without HTML escaping. Attacker-controlled feature.properties values from a published writable vector layer reach resources/server/api/ogc/templates/wfs3/getFeatures.html through QgsServerOgcApiHandler::htmlDump and the if_nullptr_null_str callback. A user who opens an items HTML page can execute stored markup or script in the QGIS Server origin, which can expose the viewer's session data or issue authenticated requests with the viewer's privileges. This issue is fixed in version 3.44.12.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 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.2%
EPSS %ILE
15th
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% 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: 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

October 12, 2026

Last Modified

October 16, 2026

Advisory Details (6)

Auto-updated Oct 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

[AgentGG] Stored XSS in WFS3 getFeatures HTML page via unescaped feature attribute values · Advisory · qgis/QGIS · GitHub

https://github.com/qgis/QGIS/security/advisories/GHSA-cr49-pm9v-m788
GitHub release Patch Available

3.44.12

Patch available: qgis/QGIS final-3_44_12

https://github.com/qgis/QGIS/releases/tag/final-3_44_12
GitHub pull request

Fix server xss

Fix merged in qgis/QGIS PR #67044 on 2026-08-13 — awaiting tagged release

https://github.com/qgis/QGIS/pull/67044
GitHub pull request

Add inja escape() function to HTML escape values

Fix merged in qgis/QGIS PR #66616 on 2026-07-01 — awaiting tagged release

https://github.com/qgis/QGIS/pull/66616
GitHub commit Patch Available

commit ca76fcac616d (qgis/QGIS)

Patch available: qgis/QGIS final-3_44_12 (contains commit ca76fcac616d)

https://github.com/qgis/QGIS/commit/ca76fcac616dbf1c0446514fd6517296eb7c6904
GitHub commit

commit 1930e81c9188 (qgis/QGIS)

Fix landed in qgis/QGIS commit 1930e81c9188 — awaiting tagged release

https://github.com/qgis/QGIS/commit/1930e81c918818a4f5412219f8f7e470d2709f91

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-10-28 01:55 UTCOSV refresh
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-10-25 14:56 UTCEG score recompute
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-18 05:09 UTCEG score recompute
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-16 16:13 UTCEG score recompute
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-13 15:27 UTCEG score recompute
Show 4 more
  1. 2026-10-13 15:07 UTCEG score recompute
  2. 2026-10-12 22:28 UTCEG score recompute
  3. 2026-10-12 22:01 UTCEG score recomputeFirst assessed: 6.1 MEDIUM
  4. 2026-10-12 21:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104140?
CVE-2026-104140 is a medium-severity vulnerability; its CVE record was published on October 12, 2026. QGIS is a free, open source, cross-platform geographic information system. Prior to 3.44.12 and 4.0.0 through 4.2.3, QGIS Server renders feature data in WFS3 (OGC API Features) HTML responses without HTML escaping. Attacker-controlled feature.properties values from a published writable vector layer…
When was the CVE record for CVE-2026-104140 published?
The CVE record for CVE-2026-104140 was published on October 12, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-104140 actively exploited?
CVE-2026-104140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104140?
CVE-2026-104140 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104140?
A fix for CVE-2026-104140 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-104140

Explore →

Is Your Infrastructure Affected by CVE-2026-104140?

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

Book a Demo →Browse All CVEs