# CVE-2025-14988: Incorrect Permission Assignment for Critical Resource vulnerability in iba Systems ibaPDA

> Unauthorized users can perform actions on the file system in ibaPDA, potentially compromising system confidentiality, integrity, and availability.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-9vq4-c9v3-2hx5

## What is CVE-2025-14988?

CVE-2025-14988 is a critical missing authorization vulnerability in ibaPDA, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain conditions. This may impact the confidentiality, integrity, or availability of the system.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-14988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14988 is a critical missing authorization vulnerability in ibaPDA, published on 27 Jan 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-2025-14988 in the wild and no public exploit code.

Affected product: ibaPDA. 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-14988/ (Markdown: https://insights.sbomify.com/CVE-2025-14988/index.md)
```

## Sources

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

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