CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NCVE-2026-79914 NocoBase: SSRF in customRequests:send via runtime options.url override
Medium (4.3) in nocobase nocobase. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @nocobase/plugin-action-custom-request 2.1.15, 2.2.0-alpha.4.
On this page
NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Versions 2.1.0 through 2.1.14 contain a server-side request forgery vulnerability in the customRequests:send endpoint. A low-privileged authenticated user can override the stored request URL at runtime using options.url, causing the NocoBase server to send requests to attacker-controlled or internal destinations. Exploitation could expose internal services, Docker host gateways, or cloud metadata endpoints and allow the server to be used as a trusted network proxy. This issue has been fixed in version 2.1.15.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-918 Server-Side Request Forgery (SSRF)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-79914 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79914?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79914?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-79914 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-79914)
HTML:
<a href="https://cve.bz/cve/CVE-2026-79914"><img src="https://cve.bz/cve/badge/CVE-2026-79914.svg" alt="CVE-2026-79914"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nocobase | >= 2.1.0, < 2.1.15 |
Fix and patched versions
@nocobase/plugin-action-custom-request(npm): fixed in 2.1.15, 2.2.0-alpha.4
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wrr5-j383-f7h2 | npm | @nocobase/plugin-action-custom-request | >=2.1.0-alpha.8 <2.1.15 | 2.1.15 |
| GHSA-wrr5-j383-f7h2 | npm | @nocobase/plugin-action-custom-request | >=2.2.0-alpha.1 <2.2.0-alpha.4 | 2.2.0-alpha.4 |
Attack patterns (CAPEC)
- CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.