topic CVE-2025-68615 Net-SNMP snmptrapd crash in General Topics

CVE-2025-68615 Net-SNMP snmptrapd crash

Blason_R — Tue, 23 Dec 2025 11:50:22 GMT

Hi Team,

It appears that CP is utilizing net-snmp, specifically version 5.8.x. Could someone verify whether this vulnerability is relevant to CP models? Given that CVSS3.1 rates it as 9.8 Critical, I am eager for a response from CP.

```

rpm -qa | grep snmp
net-snmp-libs-5.8-7.cp997000091.2.i686
net-snmp-5.8-7.cp997000091.2.i686
net-snmp-utils-5.8-7.cp997000091.2.i686
net-snmp-sysvinit-5.8-7.cp997000091.2.i686
os_net_snmp_cpis-0.1-cp997000080.i686
net-snmp-agent-libs-5.8-7.cp997000091.2.i686
os_net_snmp_config-0.1-cp997000005.i686

```

Re: CVE-2025-68615 Net-SNMP snmptrapd crash

Chris_Atkinson — Tue, 23 Dec 2025 11:58:12 GMT

Best to raise a support case with TAC for an official answer and flag with your SE if not already.

Re: CVE-2025-68615 Net-SNMP snmptrapd crash

Blason_R — Tue, 23 Dec 2025 12:05:24 GMT

Indeed, to be honest, the community is much faster than TAC. 😉

In any case, I have already contacted the local SE.

Thanks

Re: CVE-2025-68615 Net-SNMP snmptrapd crash

_Val_ — Tue, 23 Dec 2025 12:44:14 GMT

The correct way to get a security vulnerability response from Check Point is to open a ticket with TAC.

Responses in the community are not considered official unless we explicitly state that they are.

Re: CVE-2025-68615 Net-SNMP snmptrapd crash

Blason_R — Tue, 23 Dec 2025 12:45:10 GMT

Yep - already opened and following up with the TAC

Re: CVE-2025-68615 Net-SNMP snmptrapd crash

Blason_R — Thu, 25 Dec 2025 05:52:29 GMT

That's the official update from TAC. so for now I would consider no issues

@Blason_R wrote:

Yep - already opened and following up with the TAC

After thorough research, At this time, we do not have an official advisory or confirmation from Check Point specific to this CVE. However, we would like to inform you that our internal RnD teams are actively reviewing this vulnerability to assess whether it is exploitable on Check Point devices. As of now, no definitive findings or mitigation details are available. We will create an IPS protection if it is vulnerable and push via database update. Based on the current internal assessment timelines, a further update is tentatively expected by March 2026.@Blason_R wrote:

Yep - already opened and following up with the TAC