CVE-2026-47769

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. 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 weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

APIFold reads an OpenAPI 3.x or Swagger 2.x specification and generates a live, production-ready MCP server endpoint. Prior to commit 7f19b52280f414f57af2b79a95333d1c8fbeece5, the /webhooks/:serverSlug/:eventName endpoint accepts arbitrary unauthenticated JSON and stores it in Redis and the webhook_events PostgreSQL table without any signature check or authentication requirement. The root cause is that createWebhookRouter is called at server.ts:188 without a validators map, so receivers.ts:80's optional-chaining guard evaluates to undefined and the signature-validation block (receiver.ts:81–95) is unconditionally skipped. Any unauthenticated network client that knows a valid server slug can inject arbitrary payloads, which are subsequently served as trusted resource state to legitimate MCP clients. Commit 7f19b52280f414f57af2b79a95333d1c8fbeece5 patches the issue.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Unauthenticated Webhook Event Injection · Advisory · Work90210/APIFold · GitHub

https://github.com/Work90210/APIFold/security/advisories/GHSA-x82h-9r8v-m672
github_pr

fix: enforce webhook signature validation (GHSA-x82h-9r8v-m672)

Fix merged in Work90210/APIFold PR #235 on 2026-05-19 — awaiting tagged release

https://github.com/Work90210/APIFold/pull/235
github_commit

commit 7f19b52280f4 (Work90210/APIFold)

Fix landed in Work90210/APIFold commit 7f19b52280f4 — awaiting tagged release

https://github.com/Work90210/APIFold/commit/7f19b52280f414f57af2b79a95333d1c8fbeece5

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-07-28 05:25 UTCEG score recompute
  2. 2026-07-27 04:16 UTCEG score recompute
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 03:07 UTCEG score recompute
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 17:52 UTCEG score recompute
  8. 2026-07-23 17:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47769?
CVE-2026-47769 is a medium vulnerability published on July 23, 2026. APIFold reads an OpenAPI 3.x or Swagger 2.x specification and generates a live, production-ready MCP server endpoint. Prior to commit 7f19b52280f414f57af2b79a95333d1c8fbeece5, the /webhooks/:serverSlug/:eventName endpoint accepts arbitrary unauthenticated JSON and stores it in Redis and the…
When was CVE-2026-47769 disclosed?
CVE-2026-47769 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47769 actively exploited?
CVE-2026-47769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47769?
CVE-2026-47769 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47769?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47769, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47769?

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