VulnerabilityPublished 18 Jan 2026Updated 23 Feb 2026

CVE-2026-1108: cijliu librtsp · Buffer Overflow

Affects cijliu librtspSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
cijliulibrtsp	Affected =2ec1a81ad65280568a0c7c16420d7c10fde13b04	Fixed in–

AI-suggested

Conduct an immediate audit to identify all systems and applications using the cijliu librtsp library, especially those at or near the affected commit version.
Restrict local access to trusted users only, implementing strict access controls and monitoring for suspicious activity on systems running the vulnerable library.
Employ application sandboxing or containerization to limit the impact of potential exploitation.
Monitor system logs and application behavior for anomalies indicative of buffer overflow exploitation attempts or crashes.
Engage with the open source community or maintainers to track any unofficial patches or forks addressing this vulnerability.
Consider replacing or upgrading to alternative RTSP libraries with active maintenance and security support if no timely patch is forthcoming.
Implement host-based intrusion detection systems (HIDS) to detect exploitation attempts locally.
Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

A security vulnerability has been detected in cijliu librtsp up to 2ec1a81ad65280568a0c7c16420d7c10fde13b04. The affected element is the function rtsp_rely_dumps. The manipulation leads to buffer overflow. An attack has to be approached locally. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The vulnerability could allow local attackers to cause denial of service or potentially execute arbitrary code within applications using the vulnerable librtsp version. This can compromise the confidentiality, integrity, and availability of systems processing RTSP streams. Organizations that embed this library in media streaming servers, surveillance systems, or other RTSP-dependent software may face service disruptions or unauthorized access if exploited. The local access requirement limits remote exploitation, but insider threats or compromised local accounts could leverage this flaw. The lack of vendor response and patch availability increases the window of exposure. The rolling release nature of the product complicates vulnerability tracking and patch management, potentially delaying remediation. Overall, the threat is moderate but should not be ignored in environments where the library is deployed.

Summary

CVE-2026-1108 identifies a buffer overflow vulnerability in the cijliu librtsp library, specifically within the rtsp_rely_dumps function. The vulnerability arises from improper handling of input data leading to memory corruption. Exploitation requires local access with low privileges, meaning an attacker must have some level of access to the target system but does not need elevated rights or user interaction. The buffer overflow could allow an attacker to overwrite memory, potentially leading to arbitrary code execution, data corruption, or application crashes. The librtsp library is distributed via a rolling release model, which means there are no fixed version numbers for affected or patched releases, complicating vulnerability management. The vendor has not responded to disclosure attempts, and no patches or fixes have been published. The CVSS v4.0 score is 4.8 (medium), reflecting the local attack vector, low complexity, and limited scope of impact. No known public exploits exist yet, but the vulnerability poses a risk to applications relying on this library for RTSP streaming or related functions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:49 UTC

Technical details

References

Community reviews

Related threats