CWE-386: Symbolic Name not Mapping to Correct Object
Filter
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
What the weakness is: CWE-386 at MITRE. All weaknesses
Ask an AI about CWE-386
Show the prompt
Explain CWE-386: Symbolic Name not Mapping to Correct Object and how to prevent and detect it in code. Use https://cwe.mitre.org/data/definitions/386.html and https://cve.bz/cve/cwe/386?via=ask-ai-copy for recent CVEs with this weakness. Cite the sources.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this weakness's id and public links.
- 2.0CVE-2026-116486EPSS 0.1%
Objenesis before 3.6 contains a type confusion vulnerability that allows code in one class loader to substitute objects into another by exploiting instantiator caching keyed on class name. When a shared ObjenesisStd instance caches instant…
- 8.2CVE-2026-94114EPSS 0.3%
Symbolic name not mapping to correct class. BCEL caches attacker-controlled classes under their self-declared names without validating the requested name, allowing subsequent lookups and name-keyed verification results to refer to a dif…
- 7.8CVE-2026-53081EPSS 0.2%
In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsafe() compares two scalar registers that both carry BPF_ADD_CONST, check_scalar_ids() maps th…
- 7.5CVE-2024-3852EPSS 0.6%
GetBoundName could return the wrong version of an object when JIT optimizations were applied. This vulnerability affects Firefox < 125, Firefox ESR < 115.10, and Thunderbird < 115.10.