# CVE-2026-14950: Security feature bypass in FDS 102

> An attacker with a valid session ID can maintain unauthorized access to the FDS web interface after the session should have expired.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-3j24-9cjq-wm9f

## What is CVE-2026-14950?

CVE-2026-14950 is a critical vulnerability in Frauscher Sensortechnik FDS 102, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker in possession of a valid session identifier is able to continue using the session after it should have expired. This increases the risk associated with stolen, leaked, shared, or unattended sessions and may enable unauthorized continued access to the FDS web interface.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-14950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14950 is a critical vulnerability in Frauscher Sensortechnik FDS 102, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14950 in the wild and no public exploit code.

Affected product: Frauscher Sensortechnik FDS 102. 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-14950/ (Markdown: https://insights.sbomify.com/CVE-2026-14950/index.md)
```

## Sources

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

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