CVE-2026-122317 SplitPro through 2.1.6 Authorization Bypass via user.getUserDetails tRPC Query
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-122317 and fix it if it is affected.
What it is: CVE-2026-122317 is a medium-severity vulnerability in oss-apps SplitPro, published on 5 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122317 exists.
Affected product: oss-apps SplitPro. 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-122317/ (Markdown: https://insights.sbomify.com/CVE-2026-122317/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-122317?
CVE-2026-122317 is a medium-severity vulnerability in oss-apps SplitPro, published on 5 Nov 2026.
Official description
SplitPro through 2.1.6 contains an authorization bypass vulnerability that allows authenticated users to retrieve any account's details by supplying arbitrary userId values to user.getUserDetails. Attackers can iterate sequential integer user ids to harvest every user's email, name, avatar, currency, and bankingId and obapiProviderId open-banking identifiers.
Weakness: CWE-639
Which versions are affected by CVE-2026-122317?
How do I fix CVE-2026-122317?
No fix has been published for CVE-2026-122317 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-122317 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122317 exists.
Sources
Also known as GHSA-qc4q-6gxc-hfjr.