Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A silver key with the words Duplication Prohibited stamped on its bow, lying on a dark textured surface.

    Netgate pfSense CE XMLRPC flaw allows root code execution by logged-in users

    pfSense

    pfSense CE XMLRPC bug gives authenticated users root

    CVE-2026-92182 is an incorrect authorization flaw in the XMLRPC endpoint of Netgate pfSense CE. A remote attacker who can log in can use it to run arbitrary code as root on the firewall. The score is 8.8 (high) under CVSS 3.0.

    Zero Day Initiative tracked the issue as ZDI-CAN-32353 and published it as ZDI-26-960.

    Low-privilege network access is enough to reach it

    The attack comes over the network, needs no user interaction and needs only low privileges, but it does require authentication. The cause is that the XMLRPC endpoint fails to check authorization properly before it allows access to functionality. A low-privileged account can therefore reach actions it should not.

    Which pfSense CE versions are affected is not stated

    The record names Netgate pfSense CE but gives no affected version range, so you cannot tell from it whether your release is exposed. Treat any install with accounts that can reach the XMLRPC endpoint as a candidate until Netgate says otherwise. The exploitation status is unknown (the sources do not say), and unknown is not a reason to wait.

    Read Netgate advisory pfSense-SA-26_22 and update

    The record points to Netgate advisory pfSense-SA-26_22, which should carry the affected and fixed versions. No fixed version is published in the record, so check that advisory and install the release it names. Until then, review which accounts can log in to the firewall's web interface and remove any you do not need.

    What the NVD record leaves out

    The NVD entry lists its status as "Received" and gives no workaround and no disclosure or patch dates.

    Sources

    Image: Photo by Kelly Sikkema on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion