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


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-7cmc-68q2-4cf4, GHSA-98rv-h5p4-9rgr

## What is CVE-2026-127083?

CVE-2026-127083 is a medium-severity vulnerability in huginn, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-127083?

1 open source package ship an affected version, including huginn/huginn.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `huginn/huginn` | GitHub | `pkg:github/huginn/huginn` | From 2026.09.09 | 2026.11.09 |

## How do I fix CVE-2026-127083?

Upgrade huginn/huginn to 2026.11.09 or later.

## Is CVE-2026-127083 being exploited?

There is no known exploitation of CVE-2026-127083 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127083 and fix it if it is affected.

What it is: CVE-2026-127083 is a medium-severity vulnerability in huginn, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127083 in the wild and no public exploit code.

Affected packages and fixed versions:
- huginn/huginn (GitHub): affected from 2026.09.09; fixed in 2026.11.09

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127083/ (Markdown: https://insights.sbomify.com/CVE-2026-127083/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127083
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127083
- OSV: https://osv.dev/vulnerability/CVE-2026-127083

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127083/
Summaries are generated and may contain mistakes; the official description above is the record.
