Improper synchronization in Apache Netbeans HTML/Java API

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2020-17534: 0.41% estimated exploitation activity in the next 30 days; percentile 35.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

There exists a race condition between the deletion of the temporary file and the creation of the temporary directory in webkit subproject of HTML/Java API version 1.7. A similar vulnerability has recently been disclosed in other Java projects and the fix in HTML/Java API version 1.7.1 follows theirs: To avoid local privilege escalation version 1.7.1 creates the temporary directory atomically without dealing with the temporary file.

Published by the source

9 Feb 2022, 22:25 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ppc3-fpvh-7396

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-17534

Advisory: Improper synchronization in Apache Netbeans HTML/Java API
IDs: CVE-2020-17534, GHSA-ppc3-fpvh-7396
Record: https://patchnext.com/advisories/cve-2020-17534 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.netbeans.html:pom 1.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.netbeans.html:pom: affected < 1.7.1; fixed in 1.7.1

## Suggested inspection (read-only)
- Maven org.netbeans.html:pom: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.netbeans.html:pom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ppc3-fpvh-7396 (GitHub-reviewed advisory GHSA-ppc3-fpvh-7396 lists affected ranges: Maven org.netbeans.html:pom >=0 <1.7.1)

Commands are suggestions: review each one before running it.