# CVE-2026-76143: Genians, Inc Genian SSL PNS Multi Factor Authentication Bypass

> Attackers can bypass multi-factor authentication in Genian SSL PNS by manipulating login parameters, potentially gaining unauthorized access.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA: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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-83p8-vgfm-3hhr

## What is CVE-2026-76143?

CVE-2026-76143 is a high-severity missing authorization vulnerability in Genians, Inc Genian SSL PNS (frodo-core), published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing authorization vulnerability in Genian SSL PNS allows an attacker to bypass multi-factor authentication by manipulating a login request parameter.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76143 is a high-severity missing authorization vulnerability in Genians, Inc Genian SSL PNS (frodo-core), published on 1 Oct 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-76143 in the wild and no public exploit code.

Affected product: Genians, Inc Genian SSL PNS (frodo-core). 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-76143/ (Markdown: https://insights.sbomify.com/CVE-2026-76143/index.md)
```

## Sources

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

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