# CVE-2025-14758: Initialization of a Resource with an Insecure Default in YAOOK

> An on-path attacker can read database contents, including credentials, due to insecure default replication security settings in the YAOOK Operator.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-r9rc-4fcg-85c7

## What is CVE-2025-14758?

CVE-2025-14758 is a medium-severity vulnerability in ALASCA YAOOK, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect configuration of replication security in the MariaDB component of the infra-operator in YAOOK Operator allows an on-path attacker to read database contents, potentially including credentials

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2025-14758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14758 is a medium-severity vulnerability in ALASCA YAOOK, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14758 in the wild and no public exploit code.

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

## Sources

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

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