# CVE-2026-1815: Session Hijacking in TEİAŞ's Mobile Application

> Attackers can hijack user sessions due to insufficient session expiration in the TEİAŞ mobile application, leading to unauthorized account access.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-g5rh-53cq-px9w

## What is CVE-2026-1815?

CVE-2026-1815 is a medium-severity authentication bypass vulnerability in Turkiye Electricity Transmission Corporation (TEİAŞ) Mobile Application, published on 21 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Insufficient session expiration vulnerability in Turkiye Electricity Transmission Corporation (TEİAŞ) Mobile Application allows Session Hijacking.

This issue affects Mobile Application: from 1.6.2 before 1.13.

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

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


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

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

## Is CVE-2026-1815 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1815 is a medium-severity authentication bypass vulnerability in Turkiye Electricity Transmission Corporation (TEİAŞ) Mobile Application, published on 21 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1815 in the wild and no public exploit code.

Affected product: Turkiye Electricity Transmission Corporation (TEİAŞ) Mobile 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-1815/ (Markdown: https://insights.sbomify.com/CVE-2026-1815/index.md)
```

## Sources

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

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