# CVE-2025-13295: Sensitive Data Exposure in ArgusTech's BILGER

> Attackers can access sensitive information exposed in sent data due to improper message identifier selection in Argus Technology BILGER.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2025
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-pwh9-8hp5-2878

## What is CVE-2025-13295?

CVE-2025-13295 is a high-severity vulnerability in Argus Technology Inc. BILGER, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Argus Technology Inc. BILGER allows Choosing Message Identifier.

This issue affects BILGER: before 2.4.9.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-13295?

It affects 1 product.


Products: Argusteknoloji Bilger.

## How do I fix CVE-2025-13295?

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

## Is CVE-2025-13295 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13295 and fix it if it is affected.

What it is: CVE-2025-13295 is a high-severity vulnerability in Argus Technology Inc. BILGER, published on 2 Dec 2025. 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-2025-13295 in the wild and no public exploit code.

Affected product: Argus Technology Inc. BILGER. 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-2025-13295/ (Markdown: https://insights.sbomify.com/CVE-2025-13295/index.md)
```

## Sources

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

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