# CVE-2026-13483: arc53 DocsGPT Credential Storage encryption.py encrypt_credentials data authenticity

> Attackers can bypass credential storage integrity checks in DocsGPT, potentially exposing or tampering with encrypted credentials.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-v4h4-747p-qjgx

## What is CVE-2026-13483?

CVE-2026-13483 is a low-severity vulnerability in arc53 DocsGPT, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in arc53 DocsGPT up to 0.18.0. The affected element is the function encrypt_credentials of the file application/security/encryption.py of the component Credential Storage. This manipulation causes insufficient verification of data authenticity. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is described as difficult. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-13483?


## How do I fix CVE-2026-13483?

No fix has been published for CVE-2026-13483 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13483 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13483 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13483 and fix it if it is affected.

What it is: CVE-2026-13483 is a low-severity vulnerability in arc53 DocsGPT, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13483 exists.

Affected product: arc53 DocsGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13483/ (Markdown: https://insights.sbomify.com/CVE-2026-13483/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13483
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13483
- OSV: https://osv.dev/vulnerability/CVE-2026-13483

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13483/
Summaries are generated and may contain mistakes; the official description above is the record.