CVE-2026-114374: leomoon-studios wiki-go fetch-metadata Endpoint metadata_api.go server-side request forgery
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A vulnerability was identified in leomoon-studios wiki-go up to 1.9.1. This impacts an unknown function of the file internal/handlers/metadata_api.go of the component fetch-metadata Endpoint. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might be used. Upgrading to version 1.9.2 will fix this issue. The name of the patch is 25498ebf5c012b870967e38eec2a1e5133fa1a83. Upgrading the affected component is recommended.
Description quoted from the CVE record (assigned by VulDB, published 2026-10-21).
Weakness: Server-Side Request Forgery
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: GHSA-p8fx-449f-qx64
VEDAS cluster: VEDAS:DOUBLEDYNAMITE
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-114374.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-114374.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-114374.rules
Vulnerability databases and vendor advisories (2)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-p8fx-449f-qx64
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-114374
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| leomoon-studios wiki-go | version 1.9.0 version 1.9.1 | 1.9.2 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- https://github.com/leomoon-studios/wiki-go/commit/25498ebf5c012b870967e38eec2a1e5133fa1a83 (patch)
- https://github.com/leomoon-studios/wiki-go/releases/tag/v1.9.2 (patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-114374 wiki-go fetch-metadata Endpoint SSRF to Internal Address. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-114374 wiki-go fetch-metadata Endpoint SSRF to Internal Address"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/links/fetch-metadata"; fast_pattern; http.request_body; content:"url"; nocase; pcre:"/\x22url\x22\s*:\s*\x22https?:\/\/(169\.254\.169\.254|127\.|localhost|0\.0\.0\.0|10\.|192\.168\.|metadata\.|\[?::1)/i"; classtype:web-application-attack; reference:cve,CVE-2026-114374; reference:url,https://www.exploit.observer/?keyword=CVE-2026-114374&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=wiki-go&match=exact; sid:1082605; rev:1;)
CVE-2026-114374.rules on GitHub
References
Vendor advisories and patches
- https://github.com/leomoon-studios/wiki-go/commit/25498ebf5c012b870967e38eec2a1e5133fa1a83 (patch)
- https://github.com/leomoon-studios/wiki-go/releases/tag/v1.9.2 (patch)
Exploits and technical analysis
- CVE-2026-114374 | CVE Analysis and Report (third-party-advisory)
- Submit #1019388 | leomoon-studios wiki-go <= 1.9.1 Server-Side Request Forgery (third-party-advisory)
- https://github.com/leomoon-studios/wiki-go/security/advisories/GHSA-7q4p-98g4-pwp7 (exploit)
Other references
- VDB-424731 | leomoon-studios wiki-go fetch-metadata Endpoint metadata_api.go server-side request forgery (vdb-entry)
- VDB-424731 | CTI Indicators (IOB, IOC, IOA) (signature, permissions-required)
- https://github.com/leomoon-studios/wiki-go/ (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.