CWE-586: Explicit Call to Finalize()

Extended Description

While the Java Language Specification allows an object's finalize() method to be called from outside the finalizer, doing so is usually a bad idea. For example, calling finalize() explicitly means that finalize() will be called more than once: the first time will be the explicit call and the last time will be the call that is made after the object is garbage collected.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-586 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-586, Explicit Call to Finalize(), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Explicit Call to Finalize() during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Unexpected State, and Quality Degradation. Use these source-defined anchors to turn CWE-586 into implementation, review, and verification checks for the affected component.

CWE-586: Explicit Call to Finalize() — MITRE CWE

Triage CWE-586 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-586, Explicit Call to Finalize(), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-586

Apply MITRE's full root-cause mapping guidance when using CWE-586, Explicit Call to Finalize(). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-586 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-586, Explicit Call to Finalize(). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-586: Explicit Call to Finalize()?+

CWE-586: Explicit Call to Finalize() is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product makes an explicit call to the finalize() method from outside the finalizer. While the Java Language Specification allows an object's finalize() method to be called from outside the finalizer, doing so is usually a bad idea. For example, calling finalize() explicitly means that finalize() will be called more than once: the first time will be the explicit call and the last time will be the call that is made after the object is garbage collected.

What are the security consequences of Explicit Call to Finalize()?+

If exploited, CWE-586 (Explicit Call to Finalize()) it can compromise Integrity and Other, leading to outcomes such as Unexpected State and Quality Degradation.

How do you prevent or mitigate Explicit Call to Finalize()?+

Recommended mitigations for CWE-586 include: Do not make explicit calls to finalize().

Which programming languages are affected by Explicit Call to Finalize()?+

CWE-586 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-586 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-586: Explicit Call to Finalize()

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

CWE Relationships

Parent Weaknesses