CVE-2025-43708: VisiCut 2.1 allows stack consumption via an XML document with nested set elements, as demonstrated by a java.u

Routine

LOW 3.3DOWNGRADE

CVE-2025-43708 is a low-severity flaw (CVSS 3.3) affecting visicut. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

VisiCut 2.1 allows stack consumption via an XML document with nested set elements, as demonstrated by a java.util.HashMap StackOverflowError when reference='../../../set/set[2]' is used, aka an "insecure deserialization" issue.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-674
Published	2025-04-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: visicut

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-04-17 01:15 UTCPublished CVE record published
2026-06-17 09:24 UTCUpdated Record last modified

visicut visicut DOWNGRADE

Affected: 2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1

1. Check installed version

apt-cache policy visicut || rpm -q visicut || visicut --version

2. No fixed release: DOWNGRADE to a release before 2.1 (Debian / Ubuntu)

apt-cache madison visicut sudo apt install visicut=<VERSION_BEFORE_2.1> sudo apt-mark hold visicut

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list visicut sudo dnf downgrade visicut-<VERSION_BEFORE_2.1> sudo dnf versionlock add visicut

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-43708?

visicut: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-43708 being exploited?

CVE-2025-43708 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-43708 affect?

CVE-2025-43708 affects visicut. Severity is low (CVSS 3.3). VisiCut 2.1 allows stack consumption via an XML document with nested set elements, as demonstrated by a java.util.HashMap StackOverflowError when reference='../../../set/set[2]' is used, aka an "insecure deserialization" issue.

How urgent is CVE-2025-43708?

Priority 25/100. Public exploit reference

Software pages

Java vulnerabilities

Related CVEs

CVE-2025-25940 CRITICAL 9.8 DOWNGRADE VisiCut 2.1 allows code execution via Insecure XML Deserialization in the loadPlfFile method of VisicutModel.j

References

← Back to latest CVEs