Paperless-ngx's MailAccountViewSet.test() action, when called with an existing account's ID and a masked password field, reuses the stored password,… (CVE-2026-71244)
Paperless-ngx contains a vulnerability in the MailAccountViewSet.test() action where a user with limited permissions can cause stored IMAP credentials to be sent to an attacker-controlled server. This occurs because the test() action reuses stored sensitive fields like password and tokens while allowing the caller to specify the IMAP server parameters. The vulnerability allows redirection of authentication attempts without requiring full administrative privileges.
AI Analysis
Technical Summary
The vulnerability in Paperless-ngx's MailAccountViewSet.test() action (CVE-2026-71244) arises when the action is called with an existing account's ID and a masked password field. The system reuses stored sensitive credentials such as the password, account_type, refresh_token, and expiration from the existing account, but allows the caller to specify different IMAP server parameters (imap_server, imap_port, imap_security). Consequently, the test connection authenticates to the caller-specified IMAP server using the real stored credentials. A user with only object-level change_mailaccount permission (not full admin) can exploit this to redirect the authentication to an attacker-controlled IMAP host, exposing the real stored IMAP password or OAuth token to the attacker.
Potential Impact
An attacker with limited permissions can cause the system to send real stored IMAP credentials or OAuth tokens to an attacker-controlled server. This leads to credential exposure and potential unauthorized access to the victim's email account. The vulnerability does not affect system integrity or availability directly but results in a high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict the change_mailaccount permission to fully trusted users only and monitor for suspicious use of the MailAccountViewSet.test() action. Avoid allowing untrusted users to specify IMAP server parameters during test connection requests.
Paperless-ngx's MailAccountViewSet.test() action, when called with an existing account's ID and a masked password field, reuses the stored password,… (CVE-2026-71244)
Description
Paperless-ngx contains a vulnerability in the MailAccountViewSet.test() action where a user with limited permissions can cause stored IMAP credentials to be sent to an attacker-controlled server. This occurs because the test() action reuses stored sensitive fields like password and tokens while allowing the caller to specify the IMAP server parameters. The vulnerability allows redirection of authentication attempts without requiring full administrative privileges.
CVSS v3.1
Score 6.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Paperless-ngx's MailAccountViewSet.test() action (CVE-2026-71244) arises when the action is called with an existing account's ID and a masked password field. The system reuses stored sensitive credentials such as the password, account_type, refresh_token, and expiration from the existing account, but allows the caller to specify different IMAP server parameters (imap_server, imap_port, imap_security). Consequently, the test connection authenticates to the caller-specified IMAP server using the real stored credentials. A user with only object-level change_mailaccount permission (not full admin) can exploit this to redirect the authentication to an attacker-controlled IMAP host, exposing the real stored IMAP password or OAuth token to the attacker.
Potential Impact
An attacker with limited permissions can cause the system to send real stored IMAP credentials or OAuth tokens to an attacker-controlled server. This leads to credential exposure and potential unauthorized access to the victim's email account. The vulnerability does not affect system integrity or availability directly but results in a high confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict the change_mailaccount permission to fully trusted users only and monitor for suspicious use of the MailAccountViewSet.test() action. Avoid allowing untrusted users to specify IMAP server parameters during test connection requests.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-666w-8983-6664
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-71244"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a73574abf8831d53915a2b7
Added to database: 08/05/2026, 15:31:22 UTC
Last enriched: 08/05/2026, 17:43:48 UTC
Last updated: 09/19/2026, 11:33:20 UTC
Views: 66
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.