CWE-111: Direct Use of Unsafe JNI
2 CVEs have CWE-111 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 2.332%.
When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.
Child of CWE-695: Use of Low-Level Functionality
Mitigations
- Implementation: Implement error handling around the JNI call.
- Implementation: Do not use JNI calls if the native library can't be trusted.
- Implementation: Be reluctant to use JNI calls. A Java API equivalent may exist.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-111'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-111'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).