# CVE-2026-25512: Group-Office is vulnerable to RCE due to Command Injection via TNEF Attachment Handler

> An authenticated attacker can execute arbitrary system commands on Group-Office servers by injecting shell metacharacters into the TNEF attachment handler.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-579w-jvg7-frr4

## What is CVE-2026-25512?

CVE-2026-25512 is a critical command injection vulnerability in Intermesh groupoffice, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.150, 25.0.82, and 26.0.5, there is a remote code execution (RCE) vulnerability in Group-Office. The endpoint email/message/tnefAttachmentFromTempFile directly concatenates the user-controlled parameter tmp_file into an exec() call. By injecting shell metacharacters into tmp_file, an authenticated attacker can execute arbitrary system commands on the server. This issue has been patched in versions 6.8.150, 25.0.82, and 26.0.5.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Group-Office Group Office.

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

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

## Is CVE-2026-25512 being exploited?

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

Public exploit code:

- RCE - Command Injection via TNEF Attachment Handler (github_poc): https://github.com/NumberOreo1/CVE-2026-25512
- https://github.com/mbanyamer/CVE-2026-25512-PoC-Group-Office-Authenticated-RCE (github_poc): https://github.com/mbanyamer/CVE-2026-25512-PoC-Group-Office-Authenticated-RCE
- Group-Office < 26.0.5 - Remote Code Execution (nuclei): http/cves/2026/CVE-2026-25512.yaml

## Other vulnerabilities in Intermesh groupoffice

- [CVE-2026-25134](https://insights.sbomify.com/CVE-2026-25134/): Group-Office Argument Injection in MaintenanceController::actionZipLanguage (critical 9.4)
- [CVE-2025-63406](https://insights.sbomify.com/CVE-2025-63406/): Code injection in n/a (high 8.8)
- [CVE-2026-25511](https://insights.sbomify.com/CVE-2026-25511/): Group-Office is vulnerable to SSRF and File Read in WOPI service discovery (high 8.2)
- [CVE-2023-46730](https://insights.sbomify.com/CVE-2023-46730/): Server-Side Request Forgery in groupoffice (high 7.4)
- [CVE-2025-25191](https://insights.sbomify.com/CVE-2025-25191/): Group-Office has a Stored XSS Vulnerability via user's name field (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25512 is a critical command injection vulnerability in Intermesh groupoffice, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25512 exists.

Affected product: Intermesh groupoffice. 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-25512/ (Markdown: https://insights.sbomify.com/CVE-2026-25512/index.md)
```

## Sources

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

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