Security readout for executives and security teams
Plain-English summary
OSSRS SRS versions earlier than 5.0.213 reportedly contain a critical access-control flaw in RTMP publish authorization. An unauthenticated remote attacker could execute arbitrary code, potentially taking full control of a vulnerable streaming server and compromising its data, configuration, and availability.
Executive priority
Treat internet-reachable affected servers as an immediate remediation priority. The vulnerability requires no authentication or user interaction and carries potential full-system impact. Confirm exposure promptly, restrict RTMP access where feasible, and obtain vendor-confirmed remediation guidance.
Technical view
CVE-2026-68004 concerns RTMP publish authorization across vhost security configuration, security.enabled, SrsSecurity::check(), and SRS RTMP listener components. It is classified as CWE-284 with CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges or user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where OSSRS SRS earlier than 5.0.213 has a reachable RTMP listener. The supplied record does not establish whether security.enabled is a prerequisite, an affected configuration element, or one part of the vulnerable authorization path.
Exploitation context
The supplied record indicates no CISA KEV listing and provides no evidence of active exploitation. A public GitHub repository dedicated to this CVE is referenced, suggesting technical information may be public, but the bundle does not establish exploit reliability or observed attacks.
Researcher notes
Record completeness is limited: structured affected fields contain n/a and no CPEs, while the title and description identify OSSRS SRS before 5.0.213. The bundle supplies no patch commit, confirmed prerequisites, indicators of compromise, or authoritative exploitation status. Validate the version boundary against official OSSRS guidance.
Mitigation direction
- Identify all OSSRS SRS deployments and prioritize instances earlier than version 5.0.213.
- Restrict untrusted network access to RTMP listeners while remediation is assessed and deployed.
- Consult OSSRS release guidance and migrate to a vendor-confirmed non-affected release.
- Monitor vulnerable servers closely until the version and exposure risks are resolved.
Validation and detection
- Confirm the running SRS version from trusted deployment and asset records.
- Map which RTMP listeners are reachable from untrusted networks.
- Review vhost configurations for security.enabled and RTMP publish authorization usage.
- After remediation, verify the running release is vendor-confirmed as non-affected.
- Review telemetry for anomalous RTMP publishing activity; no specific indicators are supplied.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-68004 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ossrs/srs/releases/tag/v5.0-r3CVE reference, mitre
- https://github.com/xuwu-xuwu/CVE-2026-68004CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.