CVE-2026-58482

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

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

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

Network-AI, a TypeScript/Node.js multi-agent orchestrator, has a shipped, exported, documented feature called ApprovalInbox (lib/approval-inbox.ts). It is the network surface of the human-in-the-loop Approval Gate, which ApprovalGate uses to require explicit human approval for high-risk operations. The HTTP server it exposes has no authentication of any kind and sets Access-Control-Allow-Origin: * on every route, including the state-changing POST /approvals/:id/approve and /deny. As a result, in versions 5.0.0 through 5.12.1, any party who can send an HTTP request to the inbox port — a co-located process, a container/SSRF on the same host, a remote client when the operator binds a non-loopback address, or any website the operator visits in a browser (via the wildcard CORS) — can enumerate pending approvals and approve them, defeating the entire human-in-the-loop control and causing the gated high-risk action (e.g. a shell command the agent was holding for review) to execute without consent. This issue is fixed in v5.12.2. ApprovalInbox now accepts a secret option. When set, the mutating endpoints POST /:id/approve and POST /:id/deny require an Authorization: Bearer header, validated in constant time with crypto.timingSafeEqual. startServer() already binds to 127.0.0.1 by default; operators exposing the inbox on a network must set a secret.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 13, 2026

Advisory Details (3)

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

ApprovalInbox HTTP server has no authentication — anyone can approve pending agent actions · Advisory · Jovancoding/Network-AI · GitHub

Affected: v5.4.5 by requiring a secret and

https://github.com/Jovancoding/Network-AI/security/advisories/GHSA-mxjx-28vx-xjjj
github_release Patch Available

v5.12.2 — Security patch (5 CVEs)

Patch available: Jovancoding/Network-AI v5.12.2

https://github.com/Jovancoding/Network-AI/releases/tag/v5.12.2
github_commit Patch Available

commit a59c13a1f0ce (Jovancoding/Network-AI)

Patch available: Jovancoding/Network-AI v5.12.2 (contains commit a59c13a1f0ce)

https://github.com/Jovancoding/Network-AI/commit/a59c13a1f0ce0e8a0779a90343eef92fac5ab4c3

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
network-ai—5.12.2—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58482?
CVE-2026-58482 is a medium vulnerability published on July 20, 2026. Network-AI, a TypeScript/Node.js multi-agent orchestrator, has a shipped, exported, documented feature called ApprovalInbox (lib/approval-inbox.ts). It is the network surface of the human-in-the-loop Approval Gate, which ApprovalGate uses to require explicit human approval for high-risk operations.…
When was CVE-2026-58482 disclosed?
CVE-2026-58482 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58482 actively exploited?
CVE-2026-58482 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-58482?
CVE-2026-58482 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-58482?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58482, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58482?

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

Start Free Scan →Browse All CVEs