CVE-2026-61695

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-23. A secondary CVSS source baseline 7.5; sources differ by 0.0.

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

Also known asEUVD-2026-85559 (ENISA EUVD) · GHSA-86wm-r4c5-2rc9 (GitHub Security Advisories)Source: ENISA EUVD

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

A fixed version is listed under Patch Availability — apply it.

Wire provides gRPC and protocol buffers for Android, Kotlin, Swift, and Java. Prior to 6.4.1 and 7.0.0-alpha04, Wire's Swift runtime ProtoReader.skipGroup(expectedEndTag:unknownFieldsWriter:) accepts a negative length for a LENGTH_DELIMITED field inside an unknown START_GROUP field. ProtoReader.readData() forwards the negative count to ReadBuffer.readData(count:), whose upper-bound-only check permits the value to reach Foundation Data(bytes:count:) and trigger an unrecoverable process trap instead of a catchable ProtoDecoder.Error. Any Swift process decoding untrusted protobuf bytes can be crashed without authentication, user interaction, or knowledge of the target schema. This issue is fixed in versions 6.4.1 and 7.0.0-alpha04.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.
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 public PoC (CISA Vulnrichment) · Automatable yes (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 fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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: 14 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).

A fixed version is listed under Patch Availability. 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 yes (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)14 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 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

September 23, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 23, 2026
Fixed version listed under Patch Availability. Sources: github, github_pr, github_commit.
GitHub commit

commit 81ff7f24a679 (square/wire)

Fix landed in square/wire commit 81ff7f24a679 — awaiting tagged release

https://github.com/square/wire/commit/81ff7f24a6795d9a8be2e03f272b2d979a5d2c7e
GitHub commit

commit 24043b6b3a5e (square/wire)

Fix landed in square/wire commit 24043b6b3a5e — awaiting tagged release

https://github.com/square/wire/commit/24043b6b3a5e5974a978f2745b76d50b31407c1c
GitHub pull request

Add negative-length check in skipGroup for the Swift runtime

Fix merged in square/wire PR #3616 on 2026-06-17 — awaiting tagged release

https://github.com/square/wire/pull/3616
GitHub advisoryMentions a patch (unverified)

Wire Swift runtime: negative LENGTH_DELIMITED length in skipGroup() crashes any protobuf-decoding service (Swift sibling of GHSA-7xpr-hc2w-34m9) · Advisory · square/wire · GitHub

https://github.com/square/wire/security/advisories/GHSA-86wm-r4c5-2rc9

Vendor Advisories for CVE-2026-61695(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
swiftgithub.com/square/wire @ 6.4.1 (fixes <= 6.4.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-61695?
CVE-2026-61695 is a high-severity vulnerability; its CVE record was published on September 23, 2026. Wire provides gRPC and protocol buffers for Android, Kotlin, Swift, and Java. Prior to 6.4.1 and 7.0.0-alpha04, Wire's Swift runtime ProtoReader.skipGroup(expectedEndTag:unknownFieldsWriter:) accepts a negative length for a LENGTH_DELIMITED field inside an unknown START_GROUP field.…
When was the CVE record for CVE-2026-61695 published?
The CVE record for CVE-2026-61695 was published on September 23, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61695 actively exploited?
CVE-2026-61695 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61695?
CVE-2026-61695 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61695?
A fixed version for CVE-2026-61695 is listed under Patch Availability on this page: update to the version listed for your package. The vendor advisories EchelonGraph has for CVE-2026-61695 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61695?

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