Quick answers
- Is CVE-2026-8193 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8193 being exploited in the wild.
- How severe is CVE-2026-8193?
- Medium severity, with a CVSS score of 6.3, published 9 May 2026.
- Which products and versions are affected?
- Akaunting 3.1.21.
- Is there a fix for CVE-2026-8193?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-8193 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-8193?
- Check whether you run Akaunting 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
A Server-Side Request Forgery (SSRF) vulnerability exists in Akaunting 3.1.21 within the Invoice PDF Rendering component. The issue stems from improper handling of input processed by the dompdf library, specifically involving the 'config/dompdf.php' file. A remote attacker with low-level privileges can manipulate invoice data (such as unsanitized notes containing HTML) to force the server to make unauthorized requests to internal or external resources. This can lead to internal port scanning or information disclosure. A public proof-of-concept exploit has been released, and as of the advisory date, the vendor has not responded to disclosure attempts.
Affected products
- Akaunting Akaunting 3.1.21
Timeline
- 2026-05-09: disclosed: Initial disclosure and NVD publication
- 2026-05-09: other: Public exploit made available