CVE-2026-25550

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-04. A secondary CVSS source baseline 9.8; sources differ by 0.0.

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

Also known asEUVD-2026-34304 (ENISA EUVD) · GHSA-2q9g-666g-vcp9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Upgrade affected installations to BarTender 12.0.1 or later (from the CVE record's solution, VulnCheck) — apply it.

Seagull Software BarTender 2010, 2016, and 2019 contain an unauthenticated remote code execution vulnerability in the .NET Remoting service exposed on TCP port 7375 via BtSystem.Service.exe. The service registers an unauthenticated singleton endpoint — BarTenderSystem for BarTender 2016 <= R9, and DataServiceSingleton for BarTender 2019 <= R10 — configured with BinaryServerFormatterSinkProvider and TypeFilterLevel set to Full. An unauthenticated remote attacker can exploit .NET Remoting object unmarshalling to read or write arbitrary files on the server using the .NET WebClient class, or coerce NTLMv2 authentication by supplying a UNC path to an attacker-controlled server, enabling sensitive credential disclosure, remote code execution, or lateral movement depending on service account privileges and network environment. The service runs in the context of NT AUTHORITY\\SYSTEM. This vulnerability is corrected in BarTender 12.0.1. Users of affected releases should upgrade to BarTender 12.0.1 or later.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: Upgrade affected installations to BarTender 12.0.1 or later (from the CVE record's solution, VulnCheck). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

Upgrade affected installations to BarTender 12.0.1 or later (from the CVE record's solution, VulnCheck). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 4, 2026

Last Modified

September 16, 2026

Advisory Details (3)

Auto-updated Nov 8, 2026
Fix named in the CVE record's solution (VulnCheck).
Web page

Seagull Software BarTender Unauthenticated RCE via .NET Remoting Service | Advisories | VulnCheck

https://www.vulncheck.com/advisories/seagull-software-bartender-unauthenticated-rce-via-net-remoting-service
Web page

Seagull BarTender - CVE-2026-25550 / CVE-2026-25551 · GitHub

https://gist.github.com/VAMorales/dde5b1c0415a8505ccd6fafdb095a618

Vendor Advisories for CVE-2026-25550(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 100 of 557 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 457 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-13 05:16 UTCEchelonGraph re-scored
  3. 2026-11-13 05:16 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-11-12 07:18 UTCEchelonGraph re-scored
  6. 2026-11-12 07:18 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-11-11 09:21 UTCEchelonGraph re-scored
  9. 2026-11-11 09:21 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-11-10 11:23 UTCEchelonGraph re-scored
  12. 2026-11-10 11:23 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-11-09 13:26 UTCEchelonGraph re-scored
  15. 2026-11-09 13:26 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-11-08 15:29 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-07 17:32 UTCEchelonGraph re-scored
  19. 2026-11-07 17:32 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-11-06 19:35 UTCEchelonGraph re-scored
  22. 2026-11-06 19:35 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-11-05 21:38 UTCEchelonGraph re-scored
  25. 2026-11-05 21:38 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-04 23:30 UTCEchelonGraph re-scored
  3. 2026-11-04 23:30 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-11-04 01:31 UTCEchelonGraph re-scored
  6. 2026-11-04 01:31 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-11-03 03:34 UTCEchelonGraph re-scored
  9. 2026-11-03 03:34 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-11-02 05:37 UTCEchelonGraph re-scored
  12. 2026-11-02 05:36 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-11-01 07:39 UTCEchelonGraph re-scored
  15. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-10-31 09:41 UTCEchelonGraph re-scored
  18. 2026-10-31 09:41 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  20. 2026-10-30 11:44 UTCEchelonGraph re-scored
  21. 2026-10-30 11:44 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-10-29 13:48 UTCEchelonGraph re-scored
  24. 2026-10-29 13:48 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  26. 2026-10-28 15:47 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-27 17:50 UTCEchelonGraph re-scored
  28. 2026-10-27 17:50 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  30. 2026-10-26 19:53 UTCEchelonGraph re-scored
  31. 2026-10-26 19:53 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  33. 2026-10-25 19:38 UTCEchelonGraph re-scored
  34. 2026-10-25 19:38 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  36. 2026-10-25 14:40 UTCEchelonGraph re-scored
  37. 2026-10-24 21:37 UTCEchelonGraph re-scored
  38. 2026-10-24 21:37 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  40. 2026-10-23 23:40 UTCEchelonGraph re-scored
  41. 2026-10-23 23:40 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  43. 2026-10-23 01:04 UTCEchelonGraph re-scored
  44. 2026-10-23 01:04 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  46. 2026-10-22 02:20 UTCEchelonGraph re-scored
  47. 2026-10-22 02:20 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  49. 2026-10-21 04:01 UTCEchelonGraph re-scored
  50. 2026-10-21 04:00 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  52. 2026-10-20 06:02 UTCEchelonGraph re-scored
  53. 2026-10-20 06:01 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  55. 2026-10-19 08:01 UTCEchelonGraph re-scored
  56. 2026-10-19 08:01 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  58. 2026-10-18 09:53 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-18 03:52 UTCEchelonGraph re-scored
  60. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  61. 2026-10-17 06:27 UTCEchelonGraph re-scored
  62. 2026-10-17 06:27 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  64. 2026-10-16 07:50 UTCEchelonGraph re-scored
  65. 2026-10-16 07:50 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  67. 2026-10-15 06:50 UTCEchelonGraph re-scored
  68. 2026-10-15 06:50 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  70. 2026-10-14 02:35 UTCEchelonGraph re-scored
  71. 2026-10-14 02:34 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  73. 2026-10-12 22:48 UTCEchelonGraph re-scored
  74. 2026-10-12 22:48 UTCGHSA enrichmentGHSA-2q9g-666g-vcp9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile

Frequently asked(5)

What is CVE-2026-25550?
CVE-2026-25550 is a critical-severity vulnerability; its CVE record was published on June 4, 2026. Seagull Software BarTender 2010, 2016, and 2019 contain an unauthenticated remote code execution vulnerability in the .NET Remoting service exposed on TCP port 7375 via BtSystem.Service.exe. The service registers an unauthenticated singleton endpoint — BarTenderSystem for BarTender 2016 <= R9, and…
When was CVE-2026-25550 made public?
CVE-2026-25550 was made public on June 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 4, 2026. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-25550 actively exploited?
CVE-2026-25550 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25550?
CVE-2026-25550 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-25550?
The CVE record's solution for CVE-2026-25550, written by its CNA VulnCheck, names the fix: "Upgrade affected installations to BarTender 12.0.1 or later." The vendor advisories EchelonGraph has for CVE-2026-25550 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-25550?

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