CVE-2026-1109VulnerabilityPublished 18 Jan 2026Updated 23 Feb 2026

CVE-2026-1109: cijliu librtsp · Buffer Overflow

Affects cijliu librtspSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 06:26 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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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

Organizations should first identify all instances of the cijliu librtsp library in their environments, particularly those handling RTSP streaming. Given the lack of official patches, consider applying manual code review and hardening around the rtsp_parse_request function to validate input lengths and prevent buffer overflows. Employ runtime protections such as Address Space Layout Randomization (ASLR), stack canaries, and memory protection mechanisms to mitigate exploitation impact. Restrict local access to trusted users only and monitor for unusual local activity that might indicate exploitation attempts. If possible, isolate RTSP services using librtsp in sandboxed or containerized environments to limit damage scope. Engage with the vendor or community for updates or unofficial patches. Finally, maintain robust system and application logging to detect anomalous behavior related to RTSP parsing.

Description

A vulnerability was detected in cijliu librtsp up to 2ec1a81ad65280568a0c7c16420d7c10fde13b04. The impacted element is the function rtsp_parse_request. The manipulation results in buffer overflow. Attacking locally is a requirement. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The buffer overflow vulnerability could allow a local attacker to corrupt memory, potentially leading to denial of service or partial unauthorized access to sensitive information. While exploitation requires local access, the impact on confidentiality, integrity, and availability is partial but non-negligible. Systems running RTSP streaming services or media servers embedding librtsp may experience crashes or unexpected behavior, disrupting service availability. In environments where RTSP is used for surveillance, media delivery, or real-time streaming, this could degrade operational reliability. The absence of vendor patches and public exploits means the threat is currently theoretical but could be weaponized if combined with other vulnerabilities or privilege escalation techniques. Organizations with multi-user systems or shared hosting environments are at increased risk due to the local attack requirement.

Summary

CVE-2026-1109 identifies a buffer overflow vulnerability in the rtsp_parse_request function of the cijliu librtsp library, specifically up to commit 2ec1a81ad65280568a0c7c16420d7c10fde13b04. The vulnerability arises from improper handling of input data during RTSP request parsing, allowing a local attacker with low privileges to overflow a buffer. This can lead to memory corruption, potentially enabling partial compromise of confidentiality, integrity, or availability of the affected system. The vulnerability requires local access, no user interaction, and no elevated privileges beyond low-level local permissions. The CVSS 4.8 score reflects the limited attack vector and partial impact. No known exploits have been reported in the wild, but the vulnerability remains a concern for environments embedding librtsp for RTSP streaming functionality. The lack of vendor engagement and patch availability increases risk for organizations relying on this library.

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