Quick answers
- Is CVE-2026-41935 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41935 being exploited in the wild.
- How severe is CVE-2026-41935?
- High severity, with a CVSS score of 7.1, published 14 May 2026.
- Which products and versions are affected?
- Givanz VvvebJs before 1.0.8.3; Vvveb < 1.0.8.3.
- Is there a fix for CVE-2026-41935?
- A patch was published on 2026-05-13: Version 1.0.8.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41935 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41935?
- Check whether you run Givanz VvvebJs or Vvveb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An uncontrolled recursion vulnerability exists in the Vvveb admin controller dispatch cycle prior to version 1.0.8.3. The root cause is located in the Base::init() function, which repeatedly invokes the permission() method on error handlers when a user attempts to access forbidden URLs. This creates an infinite recursion loop that consumes PHP memory until limits are exhausted. A remote attacker with low-privileged credentials can exploit this by sending sustained requests to restricted admin paths, effectively crashing all PHP worker processes and causing a denial-of-service (DoS). The issue was addressed in version 1.0.8.3 by modifying the Error403 controller to no longer extend the vulnerable Base class.
Affected products
- givanz Vvveb before 1.0.8.3
Timeline
- 2026-05-13: patched: Version 1.0.8.3 released
- 2026-05-14: disclosed: Initial disclosure by VulnCheck
- 2026-05-14: advisory: CVE-2026-41935 published