Quick answers
- Is CVE-2026-13483 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13483 being exploited in the wild.
- How severe is CVE-2026-13483?
- Low severity, with a CVSS score of 3.1, published 28 June 2026.
- Which products and versions are affected?
- Arc53 DocsGPT up to 0.18.0.
- Is there a fix for CVE-2026-13483?
- 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-13483 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-13483?
- Check whether you run Arc53 DocsGPT 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 vulnerability exists in the `encrypt_credentials` function within `application/security/encryption.py` of arc53 DocsGPT. The application utilizes AES-CBC encryption for stored credentials without an accompanying Message Authentication Code (MAC) or integrity tag. This lack of authenticated encryption allows a remote attacker with low privileges to perform bit-flipping attacks on the Initialization Vector (IV) or ciphertext to make controlled changes to the decrypted plaintext. An exploit has been published demonstrating that modifying the IV can successfully alter the resulting JSON object upon decryption. A pending pull request (#2331) migrates the encryption to AES-GCM to provide the necessary integrity protections.
Affected products
- arc53 DocsGPT up to 0.18.0
Timeline
- 2026-03-26: other: Pull request to fix the issue submitted
- 2026-05-26: disclosed: Issue publicly reported on GitHub
- 2026-06-28: advisory: CVE published and NVD record created