CVE-2026-77767

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-08-21. 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
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate 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.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Reconmap's API applies a fallback authorization policy in apps/api/app/Program.cs that requires an authenticated user holding the administrator role, so controllers without their own attribute reject anonymous callers. The report preview action in apps/api/app/Controllers/ReportsController.cs carries [AllowAnonymous] and therefore opts out of that policy. PreviewReport loads the Project row named by the id path segment, loads the linked Organisation through the project's ClientId, and renders both into default-report-template.html, which prints the project name and description together with the client organisation's name, address and URL. No authentication, project membership or role check is performed. Because the id is the auto-increment primary key of the project table, an unauthenticated remote caller can walk sequential ids to retrieve the engagement details and client organisation of every project on the instance, and the 404 returned for a missing id reveals which project ids exist. Reconmap stores penetration-testing engagements, so the disclosed descriptions and client records are sensitive by nature.

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 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)
Severity75% × 45%
The EG Score, 7.5 of 10.
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 fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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.

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

August 21, 2026

Last Modified

September 24, 2026

Advisory Details (6)

Auto-updated Aug 21, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
Web page

Reconmap Report Preview Endpoint Is Marked AllowAnonymous, Exposing Every Project and Client Organisation Without Authentication | Advisories | VulnCheck

https://www.vulncheck.com/advisories/reconmap-report-preview-endpoint-is-marked-allowanonymous-exposing-every-project-and-client-organisation-without-authentication
GitHub advisoryMentions a patch (unverified)

Unauthenticated disclosure of any project and client organisation via report preview endpoint · Advisory · reconmap/reconmap · GitHub

https://github.com/reconmap/reconmap/security/advisories/GHSA-mhrh-jfmr-8mmw
GitHub commit

commit 2b2eb0cf0aa9 (reconmap/reconmap)

Fix landed in reconmap/reconmap commit 2b2eb0cf0aa9 — awaiting tagged release

https://github.com/reconmap/reconmap/commit/2b2eb0cf0aa95726b4edd0045f86d2dcdb8de34d
Web page

reconmap/apps/api/app/Program.cs at 56ca3748343a50c98185d53827172d8f13a6ad0f · reconmap/reconmap · GitHub

https://github.com/reconmap/reconmap/blob/56ca3748343a50c98185d53827172d8f13a6ad0f/apps/api/app/Program.cs
Web page

reconmap/apps/api/app/Controllers/ReportsController.cs at 56ca3748343a50c98185d53827172d8f13a6ad0f · reconmap/reconmap · GitHub

https://github.com/reconmap/reconmap/blob/56ca3748343a50c98185d53827172d8f13a6ad0f/apps/api/app/Controllers/ReportsController.cs
Web page

GitHub - reconmap/reconmap: Reconmap is a collaboration-first security operations platform for infosec teams and MSSPs, enabling end‑to‑end engagement management, from reconnaissance through execution and reporting. With built-in command automation, output parsing, and AI‑assisted summaries, it delivers faster, more structured, and high‑quality security assessments. · GitHub

https://github.com/reconmap/reconmap

Vendor Advisories for CVE-2026-77767(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 21× in last 7d / 98× 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 99 of 179 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77767?
CVE-2026-77767 is a high-severity vulnerability; its CVE record was published on August 21, 2026. Reconmap's API applies a fallback authorization policy in apps/api/app/Program.cs that requires an authenticated user holding the administrator role, so controllers without their own attribute reject anonymous callers. The report preview action in apps/api/app/Controllers/ReportsController.cs…
When was CVE-2026-77767 made public?
CVE-2026-77767 was made public on August 20, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 21, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-77767 actively exploited?
CVE-2026-77767 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77767?
CVE-2026-77767 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-77767?
A fix for CVE-2026-77767 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-77767 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77767?

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

Book a Demo →Browse All CVEs