Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-45809: OpenSIPS watcherinfo generation stack buffer overflow DoS

Published Aug 4, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS0.64%51st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-45809CWE-121 · Stack-based Buffer Overflow

CVE-2026-45809 is a denial-of-service vulnerability in OpenSIPS, a SIP server implementation. It affects versions prior to 3.6.6 and 4.0.0-rc1, including reported affected ranges starting at 3.4.0 in the 3.x branch and 4.0.0-beta in the 4.0 branch. The flaw resides in watcherinfo generation for presence.winfo. An attacker can send a SUBSCRIBE request for the presence event with an excessively long From URI, causing OpenSIPS to store an oversized watcher entry. When watcherinfo XML is later generated for the same presentity, OpenSIPS copies the stored watcher URI into a fixed-size stack buffer, resulting in a stack-based buffer overflow and process crash. The vulnerability is remotely reachable in deployments where SUBSCRIBE handling is exposed and watcherinfo generation is enabled.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes denial of service by crashing an OpenSIPS worker process. The available information indicates impact on availability rather than confidentiality or integrity. In exposed deployments, a remote unauthenticated attacker can repeatedly trigger worker crashes, potentially degrading or interrupting SIP presence-related service handling.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or restricting presence.winfo watcherinfo generation, limiting access to SUBSCRIBE handling paths, and reviewing whether the presence and presence_xml modules are necessary in the deployment. Restricting reachable SUBSCRIBE routing and filtering malformed or unusually long SIP header values may reduce exploitability, though upgrading remains the definitive fix.

Remediation

Patch, then assume compromise.

Upgrade OpenSIPS to version 3.6.6 or later in the 3.x branch, or to 4.0.0-rc1 or later in the 4.0 branch, where the vulnerability has been fixed. Ensure all affected deployments are updated to a non-vulnerable release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-45809 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-45809 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-45809?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-45809.
Is there a patch for CVE-2026-45809?
Upgrade OpenSIPS to version 3.6.6 or later in the 3.x branch, or to 4.0.0-rc1 or later in the 4.0 branch, where the vulnerability has been fixed. Ensure all affected deployments are updated to a non-vulnerable release.
How severe is CVE-2026-45809?
CVE-2026-45809 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.64% (51st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.