Repository navigation
CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7 #473
Description
Activity
- changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Jul 23, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 19, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 19, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 19, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 21, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 26, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 26, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 27, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 27, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 27, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 27, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Aug 28, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Aug 28, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Sep 4, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Sep 4, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Sep 17, 2026 - changed the title
[-]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/-][+]CVE-2026-44687 (Low) detected in src4.0.4[/+]on Sep 17, 2026 ✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
- changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4[/-][+]CVE-2026-44687 (Low) detected in src4.0.4 - autoclosed[/+]on Sep 18, 2026 ✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
- changed the title
[-]CVE-2026-44687 (Low) detected in src4.0.4 - autoclosed[/-][+]CVE-2026-44687 (Low) detected in freebsd-srcrelease/15.0.0-p7[/+]on Oct 7, 2026 ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.
CVE-2026-44687 - Low Severity Vulnerability
The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....
Library home page: https://github.com/freebsd/freebsd-src.git
Found in base branches: stable/4.0, master
In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone).
Publish Date: 2026-07-22
URL: CVE-2026-44687
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.Step up your Open Source Security Game with Mend here