ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-45254

In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected.

Published May 21, 2026 · catalog updated Jul 23, 2026 · In the case of

Check if you run it

No confirmed exploitation is on record for CVE-2026-45254. EPSS is 0.29%. Act only if a listed version of In the case of is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (In the case of).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.29%
Remediation
Advisory link
Affected products
cpe freebsd/freebsd

In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected. In certain scenarios, an application that had previously restricted a subset of network operations could ask for a new limit that extended the permissions of the process.

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.

  • cpe freebsd/freebsd14.3

How to fix CVE-2026-45254

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-45254. EPSS is 0.29%. Act only if a listed version of In the case of is installed.

Which versions are affected?

Compare what you have installed with 14.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-269: Improper Privilege Management. EPSS 0.29%. 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.

  1. May 21, 2026 · NIST NVD

    Detected

    In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected. In certain scenarios, an application that had previously restricted a subset of network operations could ask for a new limit that extended the permissions of the process.

  2. Jul 23, 2026 · NIST NVD

    Updated

    In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected. In certain scenarios, an application that had previously restricted a subset of network operations could ask for a new limit that extended the permissions of the process.

Sources

  • CVE.orgVulnerability recordCVE-2026-45254

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-45254

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-45254

    In the case of the cap_net service, when a key present in the old limit was omitted from the new limit, the missing key was treated as "allow any" instead of being rejected. In certain scenarios, an application that had previously restricted a subset of network operations could

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.