CVE-2026-1465
Improper Memory Buffer Restriction in anyRTC-RTMP-OpenSource
Publication date: 2026-01-27
Last updated on: 2026-01-27
Assigner: Government Technology Agency of Singapore Cyber Security Group (GovTech CSG)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anyrtcio-community | anyrtc-rtmp-opensource | to 1.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an improper restriction of operations within the bounds of a memory buffer in the anyRTC-RTMP-OpenSource project, specifically in the third_party/faad2-2.7/libfaad modules. It is essentially a buffer overflow issue inherited from the faad2 codebase that was not patched in anyRTC. This means that the software does not properly limit operations to the allocated memory buffer, which can lead to memory corruption or unexpected behavior. [1]
How can this vulnerability impact me? :
The buffer overflow vulnerability can lead to serious security risks such as memory corruption, which attackers could exploit to execute arbitrary code, cause crashes, or escalate privileges. This can compromise the integrity and availability of the affected system or application. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update anyRTC-RTMP-OpenSource to include the security patch merged in pull request #166 on the project's GitHub repository. This patch applies fixes originally developed for the faad2 project to eliminate the buffer overflow vulnerabilities. Applying this patch or upgrading to a version that includes it will address the issue. [1]