Huginn before 2026.11.05 Stored XSS via OAuth Service Display Name
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.11.05
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.11.05.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Huginn contains a stored cross-site scripting flaw in how it displays OAuth service display names, letting a remote attacker with a low-privilege account run JavaScript in a victim's browser after the victim attaches the crafted account to an Agent and views it. The script could expose Credentials, Agents, and Events, and could perform admin actions if the victim is an administrator.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Huginn before 2026.11.05 contains a stored cross-site scripting vulnerability in the service_label helper that marks unescaped OAuth service display names as html_safe. Authenticated attackers can connect an OAuth account with a crafted nickname, name or email and share it globally, executing JavaScript when victims attach it to Agents and view them, exposing Credentials, Agents and Events, and admin actions if the victim is an administrator.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- 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
What to do
Upgrade to a fixed version: 2026.11.05.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- huginn huginn
fixed in 2026.11.05
Evidence 7
- Advisory
- Patch
- Repository
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123094
Is CVE-2026-123094 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-123094?
huginn: before 2026.11.05.Source: cve.now feed data
How do I fix CVE-2026-123094?
Upgrade to a fixed version: 2026.11.05.Source: cve.now feed data