Credential tampering via tagless AES-CBC encryption
Published Jun 28, 2026 · Updated Jun 28, 2026
Credential-integrity failure in Arc53 DocsGPT 0.1 through 0.18.0 allows remote authenticated users to alter stored secrets. The encrypt_credentials helper in application/security/encryption.py uses AES-CBC with custom padding but no authentication tag, so IV bit flips produce controlled changes in decrypted JSON without rejection. Reachability requires low-privileged application access plus the ability to modify an encrypted credential blob; the demonstrated consequence is tampering with API tokens or connector credentials.
Summary
What happened
Credential-integrity failure in Arc53 DocsGPT 0.1 through 0.18.0 allows remote authenticated users to alter stored secrets. The encrypt_credentials helper in application/security/encryption.py uses AES-CBC with custom padding but no authentication tag, so IV bit flips produce controlled changes in decrypted JSON without rejection. Reachability requires low-privileged application access plus the ability to modify an encrypted credential blob; the demonstrated consequence is tampering with API tokens or connector credentials.
The record
- CVE
- CVE-2026-13483
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- Arc53
- Product
- DocsGPT
- Classifications
- CWE-345, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1
- Affected versionversion=0.10
- Affected versionversion=0.11
- Affected versionversion=0.12
- Affected versionversion=0.13
- Affected versionversion=0.14
- Affected versionversion=0.15
- Affected versionversion=0.16
- Affected versionversion=0.17
- Affected versionversion=0.18.0
- Affected versionversion=0.2
- Affected versionversion=0.3
- Affected versionversion=0.4
- Affected versionversion=0.5
- Affected versionversion=0.6
- Affected versionversion=0.7
- Affected versionversion=0.8
- Affected versionversion=0.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Stored credential IV bit-flip proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo