Skip to main content
Mallory
UnratedVulnerability

CVE-2026-127742: SNMPv3 Authentication and Access-Control Bypass in FreeBSD bsnmpd

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 5 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-127742CWE-306

CVE-2026-127742 is an authentication and access-control bypass in FreeBSD's bsnmpd SNMP daemon. The daemon skips User-based Security Model (USM) authentication and View-based Access Control Model (VACM) checks for SNMPv3 discovery requests, which should produce only a Report response. Vulnerable implementations nevertheless process variable bindings carried by these requests, allowing GET and SET operations without authentication or authorization. An unauthenticated remote attacker can read and modify agent-managed objects, including objects that reconfigure the daemon. The vulnerability also affects the default configuration, where the USM and VACM modules are not loaded.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can read and modify any object managed by bsnmpd, compromising the confidentiality and integrity of managed information and the agent's configuration. When the VACM module is loaded, this bypass can also provide unauthenticated access to the separate heap buffer overflow tracked as CVE-2026-127743, potentially enabling remote code execution with root privileges. Code execution is a consequence of chaining the separate overflow, not an established direct effect of CVE-2026-127742 alone.

Mitigation

If you can’t patch tonight, do this now.

Disable bsnmpd if it is not required; systems not running the daemon are unaffected. If SNMPv3 is unnecessary, restrict the daemon to SNMPv1 and SNMPv2c by adding 'begemotSnmpdVersionEnable = 3' to the %snmpd section of /etc/snmpd.config and restarting bsnmpd. This avoids CVE-2026-127742 but does not eliminate CVE-2026-127743, which remains reachable by clients with write access to the agent.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD release, including 15.1-RELEASE-p7, 14.5-RELEASE-p4, or 14.4-RELEASE-p13, or a later corrected release, and restart bsnmpd. Corrected supported stable branches are also available. Eligible systems using base system packages can run 'pkg upgrade -r FreeBSD-base'; eligible RELEASE systems using binary distribution sets can run 'freebsd-update fetch' followed by 'freebsd-update install'. Restart the daemon with 'service bsnmpd restart'. Alternatively, apply the vendor source patch after verifying its detached PGP signature, rebuild and install the operating system, and restart the applicable daemons or reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-127742 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-127742 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-127742?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-127742.
Is there a patch for CVE-2026-127742?
Upgrade to a corrected FreeBSD release, including 15.1-RELEASE-p7, 14.5-RELEASE-p4, or 14.4-RELEASE-p13, or a later corrected release, and restart bsnmpd. Corrected supported stable branches are also available.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.