The personal access token removal query selects from PersonalAccessTokenDB but filters on columns of Session, with no join between them. SQLAlchemy resolves that as an implicit cross join, so the filter does not constrain the delete to the calling user's own token in the way the code reads as intending. This way a user can delete all personal access tokens in the system.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 26 Aug 2026 08:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ericsson
Ericsson codechecker |
|
| Vendors & Products |
Ericsson
Ericsson codechecker |
Wed, 26 Aug 2026 07:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The personal access token removal query selects from PersonalAccessTokenDB but filters on columns of Session, with no join between them. SQLAlchemy resolves that as an implicit cross join, so the filter does not constrain the delete to the calling user's own token in the way the code reads as intending. This way a user can delete all personal access tokens in the system. | |
| Title | Personal access token delete filters on Session columns while deleting from PersonalAccessTokenDB | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ERIC
Published:
Updated: 2026-08-26T06:48:06.407Z
Reserved: 2026-06-29T10:41:35.472Z
Link: CVE-2026-58108
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-08-26T08:30:03Z
Weaknesses