# CVE-2026-12384: Broken Access Control in TECHIN2B Application

> Attackers can bypass authorization via user-controlled keys to abuse privileges in the TECHIN2B Application.

- **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:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-2qx2-jcc3-gvwf

## What is CVE-2026-12384?

CVE-2026-12384 is a high-severity authentication bypass vulnerability in TECHIN2B Application, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization bypass through User-Controlled key vulnerability in TECHIN2B TECHIN2B Application allows Privilege Abuse.

This issue affects TECHIN2B Application: from V1.0.7676.13 through 18092026.
NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-12384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12384 is a high-severity authentication bypass vulnerability in TECHIN2B Application, published on 18 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-12384 in the wild and no public exploit code.

Affected product: TECHIN2B Application. 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-12384/ (Markdown: https://insights.sbomify.com/CVE-2026-12384/index.md)
```

## Sources

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

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