Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-73211 – Unauthenticated SQL Injection Leading to RCE – PeerTube < 8.1.6

Be the first to know when new zero-days emerge:

Summary

CVE-2026-73211 is a critical, unauthenticated SQL injection vulnerability in PeerTube, the open-source federated video hosting platform, located in the ActorFollowModel.updateScore() function. The flaw allows a remote, unauthenticated attacker to read and write arbitrary PeerTube database tables — including OAuth access tokens — enabling full administrator account takeover and, from there, remote code execution on the host. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and has been observed being actively exploited in the wild since at least May 18, 2026.

Technical details

  • Root cause: The updateScore function of ActorFollowModel builds a SQL query using data derived from the ActivityPub actor inboxUrl field without proper sanitization/parameterization, resulting in a classic SQL injection (improper neutralization of special elements used in a SQL command).
  • Trigger conditions: A remote server can send a maliciously crafted ActivityPub "follow" request containing a malicious inboxUrl value. Because PeerTube instances process ActivityPub federation traffic from untrusted remote servers by design, no authentication or user interaction is required to reach the vulnerable code path.
  • Attack vector: Network-based (AV:N), low complexity, no privileges or user interaction required — the injection is delivered via federated ActivityPub inbox communication between PeerTube instances.
  • Impact: Successful exploitation grants arbitrary read/write access to every database table reachable by the PeerTube database role. Documented exploitation chains include:
    • Extraction of plaintext-stored OAuth access tokens to hijack existing accounts.
    • Insertion of a forged OAuth token with administrator privileges and no expiration, granting persistent admin API access.
    • Abuse of the admin-only plugin installation API to install a malicious plugin (observed in the wild as peertube-plugin-google-analytics-js), achieving remote code execution within the Node.js process.
    • In Docker-based deployments where the PostgreSQL role has elevated/superuser privileges, potential compromise of the underlying database host.
  • Observed exploitation: Public post-mortems from affected PeerTube instance operators describe active exploitation beginning around May 18, 2026 — attackers created rogue admin OAuth tokens, validated access over several days, and later used that access to push a malicious analytics plugin to compromised instances before the vendor’s public disclosure.

Affected software

  • Vendor/Product: Chocobozzz / PeerTube
  • Affected versions: All PeerTube versions prior to 8.1.6 (the vulnerable code path was reportedly introduced in December 2018)
  • Fixed versions: 8.1.6 and later (8.1.8 includes additional post-incident hardening)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade all PeerTube instances to version 8.1.6 or later (8.1.8 recommended, as it bundles additional security hardening applied after the in-the-wild exploitation). This is the only complete remediation.
  • If upgrading cannot be performed immediately:
    • Audit installed plugins for any unexpected or unrecognized entries (e.g., unauthorized analytics/tracking plugins), and remove any that were not intentionally installed.
    • Review and revoke all existing OAuth access tokens, particularly any tokens with administrator scope or no expiration date, and force administrator password resets.
    • Review database and application logs for anomalous ActivityPub follow requests with malformed or suspicious inboxUrl values, and for unexpected admin API calls (especially plugin install/update endpoints).
    • Where feasible, restrict or monitor inbound ActivityPub federation traffic from unknown/untrusted instances until patched.
    • Ensure the PostgreSQL database role used by PeerTube follows least-privilege principles (avoid superuser database accounts) to limit blast radius in containerized/Docker deployments.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge