Skip to main content
VulnerabilityPublished Updated

CVE-2023-46480: OwnCast · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Nov 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubowncast/owncastpkg:github/owncast/owncastOther threatsAffected
  • =0.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation steps include: 1) Disabling or restricting access to the indieauth function or the 'authHost' parameter if possible, until a patch is available. 2) Implementing network-level protections such as Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the 'authHost' parameter. 3) Restricting OwnCast server access to trusted IP addresses or VPNs to reduce exposure. 4) Monitoring server logs for unusual or malformed requests related to authentication functions. 5) Applying strict input validation and sanitization on parameters if custom modifications are possible. 6) Keeping OwnCast installations isolated from critical infrastructure to limit lateral movement in case of compromise. 7) Regularly backing up OwnCast configurations and data to enable recovery. Organizations should closely monitor OwnCast project updates and apply official patches as soon as they are released. Additionally, conducting penetration testing and vulnerability scanning focused on OwnCast deployments can help identify exploitation attempts.

Description

An issue in OwnCast v.0.1.1 allows a remote attacker to execute arbitrary code and obtain sensitive information via the authHost parameter of the indieauth function.

References

Community reviews

Loading reviews…