cve.bz

CVE-2026-127083 Huginn from 2026.09.09 before 2026.11.09 SSRF via OUTBOUND_PROXY Bypass

5.3 mediumEPSS 0.3%

Medium (5.3) in huginn huginn. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Huginn from 2026.09.09 before 2026.11.09 contains a server-side request forgery vulnerability because OutboundProxy.configure! applies the egress proxy only to Faraday and Typhoeus. Authenticated users can configure JiraAgent or WeiboPublishAgent to send HTTParty, open-uri or Net::HTTP requests directly to internal services, with JiraAgent returning response data as events.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

CVSS 3.1

6.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-127083 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-127083?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-127083?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-127083 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

CVE-2026-127083

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:

[![CVE-2026-127083](https://cve.bz/cve/badge/CVE-2026-127083.svg)](https://cve.bz/cve/CVE-2026-127083)

HTML:

<a href="https://cve.bz/cve/CVE-2026-127083"><img src="https://cve.bz/cve/badge/CVE-2026-127083.svg" alt="CVE-2026-127083"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
huginnfrom 2026.09.09 before 2026.11.09

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

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON