# CVE-2026-110475: Improper Authentication Vulnerability in CreditNirvana Collections Platform


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-84f2-894g-2279

## What is CVE-2026-110475?

CVE-2026-110475 is a critical vulnerability in CreditNirvana Collections Platform (CollectionWorkz), published on 26 Oct 2026. 

### Official description

This vulnerability exists in the CreditNirvana Collections Platform due to improper authentication and authorization controls at the platform login service. An unauthenticated remote attacker could exploit this vulnerability by manipulating authentication requests and accessing APIs without a valid authenticated session on the targeted system.

Successful exploitation of this vulnerability could allow the attacker to enumerate platform users, establish sessions as arbitrary users including administrative users, access and modify sensitive information with the privileges of the impersonated user.

Weakness: CWE-1390 (Weak Authentication)

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


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

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

## Is CVE-2026-110475 being exploited?

There is no known exploitation of CVE-2026-110475 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110475 is a critical vulnerability in CreditNirvana Collections Platform (CollectionWorkz), published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110475 in the wild and no public exploit code.

Affected product: CreditNirvana Collections Platform (CollectionWorkz). 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-110475/ (Markdown: https://insights.sbomify.com/CVE-2026-110475/index.md)
```

## Sources

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

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