CVE-2026-61696

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd 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
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Forem is open source software for building communities. In versions before commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c, a malicious value submitted through feedback_message[message] is stored without sanitization and rendered in app/views/admin/feedback_messages/_feedback_message.html.erb through raw(feedback_message.message) when offender_id is present. Viewing the abuse report executes arbitrary JavaScript in an administrator's browser and may expose sensitive in-page data, abuse CSRF tokens, or perform administrative actions in the victim's session. The public FeedbackMessagesController accepts the report without authorization and previously permitted a submitted offender_id, making the vulnerable rendering path reachable by an unauthenticated attacker. This issue is fixed in commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 18, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
No fix on record yet. Sources: github, github_commit.
github_commit

commit 92eacd16a82c (forem/forem)

Fix landed in forem/forem commit 92eacd16a82c — awaiting tagged release

https://github.com/forem/forem/commit/92eacd16a82cf9007ba8e16a2258b42e3b53ca9c
githubMentions a patch (unverified)

Stored XSS in Admin Abuse Report Rendering · Advisory · forem/forem · GitHub

https://github.com/forem/forem/security/advisories/GHSA-4463-499m-94mx

Weakness Classification(3)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61696?
CVE-2026-61696 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. Forem is open source software for building communities. In versions before commit 92eacd16a82cf9007ba8e16a2258b42e3b53ca9c, a malicious value submitted through feedbackmessage[message] is stored without sanitization and rendered in app/views/admin/feedbackmessages/feedbackmessage.html.erb through…
When was the CVE record for CVE-2026-61696 published?
The CVE record for CVE-2026-61696 was published on August 18, 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-61696 actively exploited?
CVE-2026-61696 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61696?
CVE-2026-61696 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61696?
No fix for CVE-2026-61696 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61696?

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

Book a Demo →Browse All CVEs