Q: Is it fixed officially? (Patch/Mitigation)

✅ **Official Fix**: **Yes**. <br>🛠️ **Patch**: The vulnerability is fixed in version **15.3.0**. <br>🔗 **Source**: See GitHub PR #2521 by Fabian Greffrath for the code changes. Update immediately to this version.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: A critical security flaw in **Woof** (a modern Doom engine).
⚠️ **Consequences**: The engine suffers from an **Out-of-Bounds Read**.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-125: Out-of-Bounds Read**.
🔍 **Flaw**: The software accesses memory outside the intended buffer boundaries.…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

👥 **Affected**: Users of **Woof** game engine.
📦 **Versions**: All versions **prior to 15.3.0**.
🏷️ **Vendor**: Developed by **Fabian Greffrath**. If you are running an older build, you are vulnerable.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Attacker Actions**:
1. **Read Sensitive Data**: Extract memory contents (High Confidentiality).
2. **Denial of Service**: Crash the application/game (High Availability).…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔓 **Exploitation Threshold**: **LOW**.
🌐 **Network**: Attack Vector is **Network (AV:N)**.
🔑 **Auth**: **None Required (PR:N)**.
👀 **UI**: **None Required (UI:N)**.
⚡ **Complexity**: **Low (AC:L)**.…

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

📂 **Public Exploit**: **No**.
🚫 **PoCs**: The `pocs` list is empty.
🔗 **References**: Only a GitHub Pull Request (PR #2521) is listed as a patch reference.…

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. **Version Check**: Verify your Woof version. If it is **< 15.3.0**, you are at risk.
2. **Log Monitoring**: Look for unexpected crashes or memory errors in the game engine logs.
3.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Official Fix**: **Yes**.
🛠️ **Patch**: The vulnerability is fixed in version **15.3.0**.
🔗 **Source**: See GitHub PR #2521 by Fabian Greffrath for the code changes. Update immediately to this version.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**:
1. **Isolate**: If possible, restrict network access to the Woof instance.
2.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
⚖️ **Priority**: CVSS Score is high due to **Network**, **Low Complexity**, and **High Impact** on Confidentiality and Availability.
📢 **Action**: Patch immediately.…

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-4750 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring