CVE-2026-85743

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th 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-118377 (ENISA EUVD)Source: ENISA EUVD

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

A fix is available — apply it.

FreeScout is a self-hosted help desk and shared mailbox. Prior to 1.8.230, multiple outbound paths in Helper::downloadRemoteFile(), Helper::checkPort(), Helper::sanitizeRemoteUrl(), MailboxesController.php, and ModulesController.php do not consistently enforce a sink-level restricted-host policy. An authenticated administrator, or another authenticated user permitted to change mailbox connection settings or trigger module update or installation paths, can supply attacker-controlled URLs or hosts. The independent download and port-test sinks can reach encoded or otherwise uncovered loopback and internal addresses. The redirect-validation bypass additionally requires a configured whitelist that permits the original and final hosts while a restricted internal host appears only as an intermediate redirect hop. No unauthenticated SSRF path is established. The server can consequently contact loopback and internal services, provide a blind internal port oracle, and retrieve internal HTTP responses into application-controlled download sinks. This issue is fixed in version 1.8.230.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 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.3%
EPSS %ILE
18th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-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.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: 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

November 6, 2026

Last Modified

November 12, 2026

Advisory Details (4)

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

Server-side request forgery via incomplete outbound host validation and unguarded download sinks · Advisory · freescout-help-desk/freescout · GitHub

https://github.com/freescout-help-desk/freescout/security/advisories/GHSA-6w8v-qp43-vg2h
GitHub release Patch Available

1.8.230

Patch available: freescout-help-desk/freescout 1.8.230

https://github.com/freescout-help-desk/freescout/releases/tag/1.8.230
GitHub commit Patch Available

commit a4c587cf1fff (freescout-help-desk/freescout)

Patch available: freescout-help-desk/freescout 1.8.230 (contains commit a4c587cf1fff)

https://github.com/freescout-help-desk/freescout/commit/a4c587cf1fff87eae7d3e4f297fa4cc81ba28704
GitHub commit Patch Available

commit 09799fd4bcf7 (freescout-help-desk/freescout)

Patch available: freescout-help-desk/freescout 1.8.230 (contains commit 09799fd4bcf7)

https://github.com/freescout-help-desk/freescout/commit/09799fd4bcf731704bc2099a87bca0cf18d20acb

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 9× 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:57 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-12 22:29 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-11 05:28 UTCEchelonGraph re-scored
  6. 2026-11-11 03:43 UTCEchelonGraph re-scored
  7. 2026-11-11 03:20 UTCEchelonGraph re-scored
  8. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-11-06 18:04 UTCENISA EUVD ID recordedEUVD-2026-118377 · Source: ENISA EUVD
  13. 2026-11-06 17:28 UTCEchelonGraph re-scored
  14. 2026-11-06 17:18 UTCEchelonGraph re-scoredFirst assessed: 8.2 HIGH
  15. 2026-11-06 17:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85743?
CVE-2026-85743 is a high-severity vulnerability; its CVE record was published on November 6, 2026. FreeScout is a self-hosted help desk and shared mailbox. Prior to 1.8.230, multiple outbound paths in Helper::downloadRemoteFile(), Helper::checkPort(), Helper::sanitizeRemoteUrl(), MailboxesController.php, and ModulesController.php do not consistently enforce a sink-level restricted-host policy.…
When was the CVE record for CVE-2026-85743 published?
The CVE record for CVE-2026-85743 was published on November 6, 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-85743 actively exploited?
CVE-2026-85743 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85743?
CVE-2026-85743 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85743?
A fix for CVE-2026-85743 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-85743

Explore →

Is Your Infrastructure Affected by CVE-2026-85743?

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

Book a Demo →Browse All CVEs