# CVE-2026-87748: Privilege Escalation via Account Takeover in Interprobe's Qorela DC

> Attackers can escalate privileges and take over accounts in Qorela DC due to missing authorization checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-7vxw-4w97-qq87

## What is CVE-2026-87748?

CVE-2026-87748 is a high-severity missing authorization vulnerability in Interprobe Information Technologies Inc. Qorela DC, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Interprobe Information Technologies Inc. Qorela DC allows Privilege Abuse.

This issue affects Qorela DC: from 1.6.1-RC29 before v1.6.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-87748 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87748 is a high-severity missing authorization vulnerability in Interprobe Information Technologies Inc. Qorela DC, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87748 in the wild and no public exploit code.

Affected product: Interprobe Information Technologies Inc. Qorela DC. 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-87748/ (Markdown: https://insights.sbomify.com/CVE-2026-87748/index.md)
```

## Sources

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

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