Vulnerability · AZL-112708
CVE-2026-0011 affecting package nmap 7.95-6
Published Mar 2, 2026 · catalog updated Nov 6, 2026 · affecting package nmap 7.95-6
Last checked Nov 7, 2026, 8 days ago.
Open the advisory
Exploitation likelihood is not on this record for AZL-112708. A missing EPSS score is not a low risk. Compare affecting package nmap 7.95-6 with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (affecting package nmap 7.95-6).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- Azure Linux:3 nmap
In enableSystemPackageLPw of Settings.java, there is a possible way to prevent location access from working due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Azure Linux:3 nmap0 → 7.95-6
How to fix AZL-112708
Upgrade
AZL-112708 lists a fix boundary at 7.95-6. Compare the installed build with that boundary before you change production.
Version check
Fixed in 7.95-6
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for AZL-112708. A missing EPSS score is not a low risk. Compare affecting package nmap 7.95-6 with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 7.95-6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Mar 2, 2026 · OpenSSF OSV / OSV Scanner
Detected
In enableSystemPackageLPw of Settings.java, there is a possible way to prevent location access from working due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Nov 6, 2026 · OpenSSF OSV / OSV Scanner
Fix available
nmap fixed in 7.95-6
Nov 6, 2026 · OpenSSF OSV / OSV Scanner
Updated
In enableSystemPackageLPw of Settings.java, there is a possible way to prevent location access from working due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryAZL-112708
CVE-2026-0011 affecting package nmap 7.95-6
osv.dev
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- OpenSSF OSV / OSV ScannerNov 7, 2026