CVE-2026-55777

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th 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
5.3EG
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.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. Prior to 1.11, the parse_ios() function uses an attacker-controlled keyword-to-OS offset as both the source offset and copy length for memmove, allowing a crafted User-Agent in a processed access log to read up to approximately 4 KB beyond the heap allocation and conditionally crash GoAccess. This issue is fixed in version 1.11.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
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.4%
EPSS %ILE
36th
KEV
Not listed

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.

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

July 30, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Out-of-bounds heap read in parse_ios() via crafted User-Agent (opesys.c:323) lead to remote crash/DoS · Advisory · allinurl/goaccess · GitHub

https://github.com/allinurl/goaccess/security/advisories/GHSA-5phr-qpgf-hgrg
GitHub commit

commit ba813ed97d99 (allinurl/goaccess)

Fix landed in allinurl/goaccess commit ba813ed97d99 — awaiting tagged release

https://github.com/allinurl/goaccess/commit/ba813ed97d998dbdcb8d87e178799a4bb2da9e81

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
goaccess1:1.10.1-1 ... 1:1.9.4-1 (9 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
goaccess1:1.10.1-1 ... 1:1.9.4-1 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
goaccess1:1.9.3-1
  • every version up to 1:1.9.3-1+deb13u1: fixed in 1:1.9.3-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
goaccess1:1.10.1-1, 1:1.9.3-1, 1:1.9.4-1
  • every version up to 1:1.11-1: fixed in 1:1.11-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 121 refreshes 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 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:goaccess

Frequently asked(5)

What is CVE-2026-55777?
CVE-2026-55777 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. Prior to 1.11, the parse_ios() function uses an attacker-controlled keyword-to-OS offset as both the source offset and copy length for memmove, allowing a crafted…
When was the CVE record for CVE-2026-55777 published?
The CVE record for CVE-2026-55777 was published on July 30, 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 8, 2026; the record at its source may have been updated since.
Is CVE-2026-55777 actively exploited?
CVE-2026-55777 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55777?
CVE-2026-55777 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55777?
A fix for CVE-2026-55777 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55777

Explore →

Is Your Infrastructure Affected by CVE-2026-55777?

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

Book a Demo →Browse All CVEs