Skip to content

Unauthenticated remote SQL injection in ActorFollowModel.updateScore()

Critical
Chocobozzz published GHSA-pqr4-34h8-g39x Jul 15, 2026

Package

No package listed

Affected versions

< 8.1.6

Patched versions

8.1.6

Description

Impact

  • Arbitrary read and write across every table the peertube DB role can reach
  • Stealth account takeover via reading plain-text OAuth access tokens from oAuthToken.accessToken; tokens survive password resets
  • Administrator takeover by overwriting the bcrypt hash for the built-in root user (universal user.id=1, hard-coded in installer.ts) — proven end-to-end with a working OAuth login
  • Post-takeover RCE inside the PeerTube Node.js process via the documented plugin install path (require(modulePath) in plugin-manager.ts)
  • Database-host RCE in the official Docker compose layout, because POSTGRES_USER=peertube creates the role as cluster superuser; COPY ... FROM PROGRAM is then reachable. The from-source install documented at support/doc/production.md does not give the role superuser, so this tier is configuration-dependent

Patches

Patched Versions: 8.1.6

Workarounds

See workarounds in v8.1.8 changelog.

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE ID

CVE-2026-73211

Weaknesses

No CWEs

Credits