# CVE-2026-2627: Softland FBackup Backup/Restore HID.dll link following

> Local attackers can exploit link following in HID.dll to escalate privileges in Softland FBackup, which currently lacks a vendor fix.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/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:** 17 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-pp6p-hwf9-pcpx

## What is CVE-2026-2627?

CVE-2026-2627 is a high-severity path traversal vulnerability in Softland FBackup, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in Softland FBackup up to 9.9. This impacts an unknown function in the library C:\Program Files\Common Files\microsoft shared\ink\HID.dll of the component Backup/Restore. The manipulation results in link following. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-2627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2627 is a high-severity path traversal vulnerability in Softland FBackup, published on 17 Feb 2026. 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-2026-2627 exists.

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

## Sources

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

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