# CVE-2025-2588: Hercules Augeas fa.c re_case_expand null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in the Augeas configuration library's re_case_expand function.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2025
- **Updated:** 21 Mar 2025
- **Also known as:** AZL-58945, AZL-58951, BELL-CVE-2025-2588, CLSA-2026-1775688216, DEBIAN-CVE-2025-2588, GHSA-hxwj-c5vw-fwgp, MGASA-2025-0128, OESA-2025-1428, SUSE-SU-2025:01534-1, SUSE-SU-2025:01754-1, SUSE-SU-2025:01763-1, SUSE-SU-2025:1413-1, SUSE-SU-2025:1534-1, SUSE-SU-2025:20345-1, SUSE-SU-2025:20415-1, UBUNTU-CVE-2025-2588, openSUSE-SU-2025:15021-1

## What is CVE-2025-2588?

CVE-2025-2588 is a medium-severity vulnerability in Hercules Augeas, published on 21 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Hercules Augeas 1.14.1 and classified as problematic. This vulnerability affects the function re_case_expand of the file src/fa.c. The manipulation of the argument re leads to null pointer dereference. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `augeas` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.10.1-150000.3.15.1 |
| `augeas` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.10.1-150000.3.15.1 |
| `augeas` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.12.0-150400.3.8.1 |
| `augeas` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.12.0-150400.3.8.1 |
| `augeas` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.12.0-150400.3.8.1 |
| `augeas` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.14.1-150600.3.3.1 |
| `augeas` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.14.1-150600.3.3.1 |
| `augeas` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.10.1-4.6.1 |
| `augeas` | SUSE:Linux Micro 6.0 | All versions | 1.14.1-2.1 |
| `augeas` | SUSE:Linux Micro 6.1 | All versions | 1.14.1-slfo.1.1_2.1 |
| `augeas` | openSUSE:Leap 15.6 | All versions | 1.14.1-150600.3.3.1 |
| `augeas` | openSUSE:Tumbleweed | All versions | 1.14.1-2.1 |

Products: Augeas Augeas.

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

Apply the vendor's patch.

## Is CVE-2025-2588 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2588 exists.

## Other vulnerabilities in Hercules Augeas

- [CVE-2017-7555](https://insights.sbomify.com/CVE-2017-7555/): Memory corruption in augeas (critical 9.8)
- [CVE-2013-6412](https://insights.sbomify.com/CVE-2013-6412/): Misconfiguration in n/a (medium 4.6)
- [CVE-2012-0787](https://insights.sbomify.com/CVE-2012-0787/): Race condition in n/a (low 3.7)
- [CVE-2012-0786](https://insights.sbomify.com/CVE-2012-0786/): Path traversal in n/a (low 3.3)
- [CVE-2012-6607](https://insights.sbomify.com/CVE-2012-6607/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2588 is a medium-severity vulnerability in Hercules Augeas, published on 21 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2588 exists.

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

## Sources

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

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