CVE-2026-113380 In the RingRTC library before 2.72.0 for Signal, a peer that saturates a call's FSM queue can interfere with the ability of a local hangup t
Critical 9.3
Published
Updated
Check this codebase for CVE-2026-113380 and fix it if it is affected.
What it is: CVE-2026-113380 is a critical vulnerability in Signal RingRTC, published on 20 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-113380 in the wild and no public exploit code.
Affected product: Signal RingRTC. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-113380/ (Markdown: https://insights.sbomify.com/CVE-2026-113380/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-113380?
CVE-2026-113380 is a critical vulnerability in Signal RingRTC, published on 20 Oct 2026.
Official description
In the RingRTC library before 2.72.0 for Signal, a peer that saturates a call's FSM queue can interfere with the ability of a local hangup to tear the call (with its audio and perhaps also video track) down.
Weakness: CWE-754
Which versions are affected by CVE-2026-113380?
How do I fix CVE-2026-113380?
No fix has been published for CVE-2026-113380 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-113380 being exploited?
There is no known exploitation of CVE-2026-113380 in the wild and no public exploit code.
Sources
Also known as GHSA-5c63-xm6f-r368.