# CVE-2026-4822: Enter Software Iperius Backup Backup Service temp file

> Local attackers can exploit insecure temporary file permissions in Iperius Backup to potentially escalate privileges.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** No
- **Published:** 25 Mar 2026
- **Updated:** 28 Mar 2026
- **Also known as:** GHSA-f8vx-q848-4v5x

## What is CVE-2026-4822?

CVE-2026-4822 is a high-severity vulnerability in Enter Software Iperius Backup, published on 25 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in Enter Software Iperius Backup up to 8.7.3. Affected is an unknown function of the file C:\ProgramData\IperiusBackup\Jobs\ of the component Backup Service. Performing a manipulation results in creation of temporary file with insecure permissions. The attack is only possible with local access. A high degree of complexity is needed for the attack. The exploitability is told to be difficult. The exploit is now public and may be used. Upgrading to version 8.7.4 is able to address this issue. It is recommended to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-378 (Creation of Temporary File With Insecure Permissions), CWE-377 (DEPRECATED: Insecure Temporary File)

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


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

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

## Is CVE-2026-4822 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4822 is a high-severity vulnerability in Enter Software Iperius Backup, published on 25 Mar 2026. 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-2026-4822 in the wild and no public exploit code.

Affected product: Enter Software Iperius Backup. 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-4822/ (Markdown: https://insights.sbomify.com/CVE-2026-4822/index.md)
```

## Sources

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

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