Huginn internal data exposed via SSRF in JiraAgent
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.11.09
- Who is exposed
- Not reported
Summary
Huginn, the agent-based automation software, is affected by a server-side request forgery flaw: an authenticated user can configure the JiraAgent or WeiboPublishAgent to send requests directly to internal services, bypassing the outbound proxy. The flaw is reached remotely over the network with low-privilege login, and it can expose internal service data, with JiraAgent returning the responses as events.
Written by a model
Original description
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.
What to do
Upgrade to a fixed version: 2026.11.09.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127083 (Huginn from 2026.09.09 before 2026.11.09 SSRF via OUTBOUND_PROXY Bypass), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127083 (entry last updated 2026-11-17):
Affected:
- huginn huginn: from 2026.09.09, fixed in 2026.11.09
Fixed versions: 2026.11.09.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127083 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127083 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/huginn/huginn/security/advisories/GHSA-98rv-h5p4-9rgr
- https://github.com/huginn/huginn/commit/a6f5fb64ac957f33fc6cdff6ab92884e372857a8
- https://github.com/huginn/huginn/blob/v2026.11.05.2/lib/outbound_proxy.rb#L38-L42
- https://github.com/huginn/huginn/blob/v2026.11.05.2/app/models/agents/jira_agent.rb#L108-L109
- https://github.com/huginn/huginn/releases/tag/v2026.11.09
- https://www.vulncheck.com/advisories/huginn-from-2026.09.09-before-2026.11.09-ssrf-via-outbound-proxy-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127083
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127083"}.Affected versions
- huginn huginnFrom 2026.09.09 · fixed in 2026.11.09
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now4 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.24%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · huginn/huginn · Advisory GHSA-98rv-h5p4-9rgr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-127083 |
| Record | NVD · CVE-2026-127083 |
| Other links 5 | |
| Patch | GitHub · huginn/huginn · Commit a6f5fb64 |
| Repository | GitHub · huginn/huginn · lib/outbound_proxy.rb · L38-L42 |
| Repository | GitHub · huginn/huginn · app/models/agents/jira_agent.rb · L108-L109 |
| Repository | GitHub · huginn/huginn · Release v2026.11.09 |
| Link | vulncheck.com · advisories/huginn-from-2026.09.09-before-2026.11.09-ssrf-via-outbound-proxy-bypass |
Questions about CVE-2026-127083
Is CVE-2026-127083 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-127083?
huginn: from 2026.09.09 before 2026.11.09.
Source: cve.now feed data
How do I fix CVE-2026-127083?
Upgrade to a fixed version: 2026.11.09.
Source: cve.now feed data
Related
- CVE-2026-127082Huginn before 2026.11.09 Information Exposure via JqAgent jq env Builtin
- CVE-2026-63769Huginn < 2026.09.09 SSRF via ScenarioImport fetch_url Method
- CVE-2026-123094Huginn before 2026.11.05 Stored XSS via OAuth Service Display Name
- CVE-2026-130235Improper Request URL Validation in the Okta .NET SDK Abstractions Library
- CVE-2026-77315Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
- CVE-2026-133235Tandoor Recipes before 2.7.4 SSRF via Nextcloud Storage WebDAV Client
No corrections so far. Something wrong on this page? Report an error.