CVE-2026-69075

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

FlowIntel is affected by a stored cross-site scripting vulnerability through multiple user-controlled or administrator-controlled fields.

Persisted values—including case titles, ticket identifiers, recurring-case information, user profile attributes, organisation names, and role names—were rendered inside DOM elements subsequently compiled by Vue. Although normal HTML escaping could neutralize direct HTML markup, it did not prevent an attacker from injecting Vue interpolation expressions using the configured [[ ... ]] delimiters.

An authenticated attacker able to modify one of the affected fields could store a malicious Vue expression. When another user viewed an affected case, report, profile, recurring-case page, or navigation component, Vue could evaluate the injected expression in the context of the FlowIntel application.

Successful exploitation could allow arbitrary JavaScript execution in the victim’s browser under the FlowIntel origin. This could expose information available to the victim, perform actions using the victim’s authenticated session, or modify application data within the victim’s privileges.

The patch introduces a dedicated vue_escape filter that escapes HTML-sensitive characters and breaks Vue interpolation delimiters before the values are rendered. The filter is applied to the affected case, account, organisation, role, configuration, and navigation fields.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100CISA SSVC

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
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit b0e99aa6d270 (flowintel/flowintel)

Fix landed in flowintel/flowintel commit b0e99aa6d270 — awaiting tagged release

https://github.com/flowintel/flowintel/commit/b0e99aa6d2708730bc422ebb6dc0c14d732389fa

Vendor Advisories for CVE-2026-69075(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 65× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 06:20 UTCEG score recompute
  3. 2026-10-04 06:20 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 10:23 UTCEG score recompute
  7. 2026-10-02 10:23 UTCGHSA enrichment
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 02:37 UTCEG score recompute
  10. 2026-10-01 02:36 UTCGHSA enrichment
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 06:42 UTCEG score recompute
  13. 2026-09-29 06:42 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-27 18:16 UTCEG score recompute
  16. 2026-09-27 18:16 UTCGHSA enrichment
  17. 2026-09-27 13:48 UTCEPSS rescore
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 05:57 UTCEG score recompute
  20. 2026-09-25 05:57 UTCGHSA enrichment
  21. 2026-09-24 05:56 UTCEG score recompute
  22. 2026-09-24 05:56 UTCGHSA enrichment
  23. 2026-09-23 17:54 UTCEPSS rescore
  24. 2026-09-23 05:34 UTCEG score recompute
  25. 2026-09-23 05:34 UTCGHSA enrichment
Show 75 more
  1. 2026-09-22 05:33 UTCEG score recompute
  2. 2026-09-22 05:33 UTCGHSA enrichment
  3. 2026-09-21 21:09 UTCEPSS rescore
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 11:07 UTCEG score recompute
  6. 2026-09-20 11:07 UTCGHSA enrichment
  7. 2026-09-19 08:00 UTCEG score recompute
  8. 2026-09-19 08:00 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 07:09 UTCEG score recompute
  11. 2026-09-18 07:09 UTCGHSA enrichment
  12. 2026-09-17 07:07 UTCEG score recompute
  13. 2026-09-17 07:07 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 07:04 UTCEG score recompute
  16. 2026-09-16 07:04 UTCGHSA enrichment
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 07:02 UTCEG score recompute
  19. 2026-09-15 07:02 UTCGHSA enrichment
  20. 2026-09-14 06:58 UTCEG score recompute
  21. 2026-09-14 06:58 UTCGHSA enrichment
  22. 2026-09-13 06:58 UTCEG score recompute
  23. 2026-09-13 06:58 UTCGHSA enrichment
  24. 2026-09-12 06:54 UTCEG score recompute
  25. 2026-09-12 06:54 UTCGHSA enrichment
  26. 2026-09-11 14:53 UTCEPSS rescore
  27. 2026-09-11 09:37 UTCEPSS rescore
  28. 2026-09-11 06:53 UTCEG score recompute
  29. 2026-09-11 06:53 UTCGHSA enrichment
  30. 2026-09-10 06:52 UTCGHSA enrichment
  31. 2026-09-09 06:47 UTCEG score recompute
  32. 2026-09-09 06:47 UTCGHSA enrichment
  33. 2026-09-08 22:01 UTCEPSS rescore
  34. 2026-09-07 18:58 UTCEG score recompute
  35. 2026-09-07 18:58 UTCGHSA enrichment
  36. 2026-09-07 16:01 UTCEPSS rescore
  37. 2026-09-06 13:47 UTCEPSS rescore
  38. 2026-09-06 10:35 UTCEG score recompute
  39. 2026-09-06 10:35 UTCGHSA enrichment
  40. 2026-09-05 15:31 UTCEPSS rescore
  41. 2026-09-05 10:34 UTCEG score recompute
  42. 2026-09-05 10:33 UTCGHSA enrichment
  43. 2026-09-04 10:17 UTCEG score recompute
  44. 2026-09-04 10:17 UTCGHSA enrichment
  45. 2026-09-04 05:07 UTCEPSS rescore
  46. 2026-09-03 08:56 UTCEG score recompute
  47. 2026-09-03 08:56 UTCGHSA enrichment
  48. 2026-09-02 14:12 UTCEPSS rescore
  49. 2026-09-01 23:15 UTCEG score recompute
  50. 2026-09-01 23:15 UTCGHSA enrichment
  51. 2026-09-01 13:54 UTCEPSS rescore
  52. 2026-09-01 04:40 UTCEPSS rescore
  53. 2026-08-31 23:13 UTCGHSA enrichment
  54. 2026-08-30 22:05 UTCEG score recompute
  55. 2026-08-30 22:05 UTCGHSA enrichment
  56. 2026-08-30 19:17 UTCEPSS rescore
  57. 2026-08-30 01:22 UTCEPSS rescore
  58. 2026-08-29 22:03 UTCEG score recompute
  59. 2026-08-29 22:03 UTCGHSA enrichment
  60. 2026-08-28 21:42 UTCEPSS rescore
  61. 2026-08-27 20:03 UTCEG score recompute
  62. 2026-08-27 20:03 UTCGHSA enrichment
  63. 2026-08-26 17:40 UTCEG score recompute
  64. 2026-08-26 17:40 UTCGHSA enrichment
  65. 2026-08-26 14:47 UTCEPSS rescore
  66. 2026-08-25 17:45 UTCEG score recompute
  67. 2026-08-25 17:45 UTCGHSA enrichment
  68. 2026-08-25 13:49 UTCEPSS rescore
  69. 2026-08-24 17:44 UTCEG score recompute
  70. 2026-08-24 17:44 UTCGHSA enrichment
  71. 2026-08-23 16:14 UTCEG score recompute
  72. 2026-08-23 16:14 UTCGHSA enrichment
  73. 2026-08-23 00:19 UTCEPSS rescore
  74. 2026-08-22 16:09 UTCEG score recompute
  75. 2026-08-22 16:09 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-69075?
CVE-2026-69075 is a medium vulnerability published on August 3, 2026. FlowIntel is affected by a stored cross-site scripting vulnerability through multiple user-controlled or administrator-controlled fields. Persisted values—including case titles, ticket identifiers, recurring-case information, user profile attributes, organisation names, and role names—were rendered…
When was CVE-2026-69075 disclosed?
CVE-2026-69075 was first published on August 3, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69075 actively exploited?
CVE-2026-69075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69075?
CVE-2026-69075 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69075?
An upstream fix for CVE-2026-69075 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-69075 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69075?

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