CVE-2026-4750VulnerabilityPublished 24 Mar 2026

CVE-2026-4750: fabiangreffrath woof · Out-of-bounds Read

Affects fabiangreffrath woofSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 15.3.0 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.3.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 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-25.

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

Upgrade fabiangreffrath/woof to 15.3.0.

Affected software

Product	Affected	Fixed in
fabiangreffrathwoof	Affected =0	Fixed in–
GitHubfabiangreffrath/woof`pkg:github/fabiangreffrath/woof`Other threats	Affected <15.3.0	Fixed in 15.3.0
GitHubwoof`pkg:github/woof`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade to woof version 15.3.0 or later as soon as the patch becomes available from the vendor to eliminate the vulnerability. 2. If you cannot patch yet, implement network-level access controls to restrict exposure of the woof service to trusted networks and users only. 3. Employ intrusion detection and prevention systems (IDS/IPS) to monitor for anomalous traffic patterns or attempts to exploit out-of-bounds reads. 4. Conduct thorough code audits and memory safety checks if custom modifications or integrations with woof exist to identify and remediate similar memory handling issues. 5. Use application-layer firewalls to filter and sanitize inputs that interact with the vulnerable component to reduce attack vectors. 6. Maintain comprehensive logging and monitoring to detect unusual application behavior or crashes indicative of exploitation attempts. 7. Educate system administrators and security teams about the vulnerability and ensure incident response plans include steps for rapid patch deployment and mitigation. 8. Consider deploying runtime application self-protection (RASP) tools that can detect and block memory access violations in real time. These targeted measures go beyond generic advice and focus on reducing exposure and preparing for rapid remediation.

Description

Out-of-bounds Read vulnerability in fabiangreffrath woof.This issue affects woof: before woof_15.3.0.

Impact

The vulnerability poses a significant risk to organizations using affected versions of fabiangreffrath woof. Successful exploitation can lead to unauthorized disclosure of sensitive information due to out-of-bounds memory reads, compromising confidentiality. Additionally, the vulnerability can cause application crashes or instability, resulting in denial of service and impacting availability. Since no authentication or user interaction is required, attackers can remotely exploit this flaw at scale, increasing the threat surface. This can disrupt critical services, especially in environments where woof is used for web or data-serving functions. The exposure of sensitive data could lead to further attacks, including privilege escalation or lateral movement within networks. Organizations in sectors such as government, finance, healthcare, and technology that rely on this software may face operational disruptions, reputational damage, and regulatory consequences if exploited. The absence of known exploits currently provides a window for proactive mitigation, but the critical severity demands urgent action to prevent potential future attacks.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/fabiangreffrath/woof/pull/2521 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 15:01 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats