CVE-2026-50190

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th 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
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 8.6Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Shaarli is a personal bookmarking service. Versions prior to 0.16.3 are vulnerable to stored XSS in application/front/controller/visitor/BookmarkListController.php. The permalink handler concatenates the raw $bookmark->getTitle() into the pagetitle template variable and the RainTPL template emits it into the document ` element without HTML escaping. A bookmark title containing ... closes the document title early and the injected script executes in the Shaarli origin for any visitor of /shaare/{hash}. Shaarli's metadata fetcher copies a remote page's ` text verbatim into the local bookmark title, so an attacker who hosts an attacker-controlled URL and convinces an administrator to bookmark it plants the payload with no further interaction — and the resulting permalink fires for every visitor including the administrator on first save, providing a one-shot administrator account takeover. Version 0.16.3 fixes the issue.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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

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

August 20, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Stored XSS via raw bookmark title in document <title> element on public permalink page · Advisory · shaarli/Shaarli · GitHub

https://github.com/shaarli/Shaarli/security/advisories/GHSA-xm98-h5jj-64xv

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
shaarli0.12.1+dfsg-8 ... 0.16.1+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
shaarli0.14.0+dfsg-1, 0.14.0+dfsg-2, 0.14.0+dfsg-2+deb13u1, 0.15.0+dfsg-1, 0.16.1+dfsg-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 50× 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-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-09 08:21 UTCEG score recompute
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-08 05:14 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-06 16:52 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-06 03:20 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-05 09:40 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-03 16:46 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-03 01:43 UTCEG score recompute
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-10-01 22:44 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
Show 69 more
  1. 2026-09-30 20:58 UTCEG score recompute
  2. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-09-30 08:10 UTCEG score recompute
  4. 2026-09-28 21:37 UTCEG score recompute
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-09-27 15:55 UTCEG score recompute
  7. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-09-27 02:56 UTCEG score recompute
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-09-24 19:54 UTCEG score recompute
  12. 2026-09-23 18:17 UTCEG score recompute
  13. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-09-22 15:31 UTCEG score recompute
  15. 2026-09-22 02:43 UTCEG score recompute
  16. 2026-09-21 00:50 UTCEG score recompute
  17. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-09-19 23:00 UTCEG score recompute
  19. 2026-09-18 20:19 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-18 05:05 UTCEG score recompute
  22. 2026-09-16 14:22 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-15 12:43 UTCEG score recompute
  26. 2026-09-13 21:28 UTCEG score recompute
  27. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-12 19:51 UTCEG score recompute
  29. 2026-09-11 18:13 UTCEG score recompute
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-10 16:34 UTCEG score recompute
  32. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-09 01:54 UTCEG score recompute
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-07 17:51 UTCEG score recompute
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-09-06 16:12 UTCEG score recompute
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-09-06 03:20 UTCEG score recompute
  40. 2026-09-05 01:43 UTCEG score recompute
  41. 2026-09-02 21:42 UTCEG score recompute
  42. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-09-01 19:54 UTCEG score recompute
  44. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-01 07:05 UTCEG score recompute
  46. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-31 04:50 UTCEG score recompute
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-30 03:13 UTCEG score recompute
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-08-29 01:28 UTCEG score recompute
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-27 18:21 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-26 16:14 UTCEG score recompute
  56. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-25 14:36 UTCEG score recompute
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-25 01:48 UTCEG score recompute
  60. 2026-08-24 12:59 UTCEG score recompute
  61. 2026-08-23 11:22 UTCEG score recompute
  62. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-22 09:45 UTCEG score recompute
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-08-21 08:07 UTCEG score recompute
  66. 2026-08-20 19:18 UTCEG score recompute
  67. 2026-08-20 19:12 UTCEG score recompute
  68. 2026-08-20 18:52 UTCEG score recomputeFirst assessed: 8.6 HIGH
  69. 2026-08-20 18:51 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50190?
CVE-2026-50190 is a high-severity vulnerability; its CVE record was published on August 20, 2026. Shaarli is a personal bookmarking service. Versions prior to 0.16.3 are vulnerable to stored XSS in application/front/controller/visitor/BookmarkListController.php. The permalink handler concatenates the raw $bookmark->getTitle() into the pagetitle template variable and the RainTPL template emits…
When was the CVE record for CVE-2026-50190 published?
The CVE record for CVE-2026-50190 was published on August 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 September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-50190 actively exploited?
CVE-2026-50190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50190?
CVE-2026-50190 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50190?
The CVE record for CVE-2026-50190 names the fix: "Version 0.16.3 fixes the issue."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50190

Explore →

Is Your Infrastructure Affected by CVE-2026-50190?

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

Book a Demo →Browse All CVEs