On this page (7 sections)

On November 15, 2026, the Debian security team published DSA-6632-1, a security update for radsecproxy, a RADIUS protocol proxy that supports RadSec. Debian says two vulnerabilities were discovered that could result in denial of service.

If you run radsecproxy on Debian 13 (trixie), for example to relay Wi-Fi or network login traffic between sites, you should plan to apply the update. The advisory is short, so this article also covers what is not yet known and how to check your own systems.

What Debian has announced

The advisory states that two vulnerabilities were found in radsecproxy and that they could lead to denial of service. For the stable distribution (trixie), Debian says the problems are fixed in version 1.11.2-1+deb13u2 and recommends upgrading the radsecproxy packages. The related Debian bug is 1154013, and the Debian security tracker is the place for ongoing status.

That is the full extent of the confirmed detail. This is one primary source, the Debian advisory itself, and no other independent coverage was available when this was written.

What is not known yet

  • CVE identifiers: the advisory lists the CVE ID as not yet available, so there are no CVE records or CVSS scores to cite.
  • Technical details: the advisory does not describe the flawed code, the trigger conditions, or whether an attacker needs authentication or a particular network position.
  • Exploitation: the advisory does not say whether the issues are being exploited, and nothing in the research indicates public exploit code.
  • Other Debian releases: the advisory only names the stable distribution (trixie). Check the security tracker for other releases you run.

Treat the impact as availability only, as Debian describes it. Do not assume more than that, and do not assume less: a denial of service in an authentication proxy can interrupt network logins that depend on it.

Why a proxy denial of service matters

RADIUS is widely used to authenticate users on Wi-Fi, VPNs and network equipment. RadSec carries RADIUS over TLS, and a proxy such as radsecproxy sits between clients and upstream servers, forwarding requests. If the proxy crashes or hangs, the services behind it may be unable to authenticate anyone until it is restarted. A denial-of-service flaw in a component like this is mainly an availability risk, which is why exposure depends on who can reach the proxy.

Who is exposed

  • Anyone running the radsecproxy package from Debian 13 (trixie) at a version older than 1.11.2-1+deb13u2.
  • Organizations that expose radsecproxy to the internet or to partner networks, such as roaming federations, are likely more exposed than those that only allow a few known peers. The advisory does not state the attack conditions, so this is a general precaution.
  • Systems that do not have radsecproxy installed are not affected by this advisory.

How to check your exposure

This read-only command lists the installed radsecproxy package and its version on Debian. If it prints nothing, the package is not installed. If the version is older than 1.11.2-1+deb13u2 on trixie, you need the update.

Check the installed radsecproxy version (Debian)Shell
dpkg -l radsecproxy

This read-only command shows whether the service is running, which tells you whether the proxy is actually in use on the host.

Check whether the radsecproxy service is active (systemd)Shell
systemctl status radsecproxy

What to do now

  1. Find every Debian host running radsecproxy, including lab, branch-office and failover systems.
  2. Confirm each host's release and installed version with dpkg -l radsecproxy.
  3. Schedule a short maintenance window, since the service restart may briefly interrupt logins.
  4. Update the package to 1.11.2-1+deb13u2 or later on trixie.
  5. Restart radsecproxy if the package update did not already do so, then confirm the service is active.
  6. Restrict who can reach the proxy port to known peers and clients with firewall rules where you can.
  7. Watch the Debian security tracker for CVE identifiers and any follow-up advisory.
Caution. Updating and restarting radsecproxy can briefly interrupt RADIUS and RadSec authentication for users and devices that rely on it. Apply the change in a maintenance window or on one node at a time if you have redundancy.

These commands refresh the package index and upgrade only the radsecproxy package on Debian.

Update only the radsecproxy package (Debian 13 trixie, run as root)Shell
apt update
apt install --only-upgrade radsecproxy

After the upgrade, run the version check again and confirm it reports 1.11.2-1+deb13u2 or newer.

Monitoring afterwards

Because the impact is denial of service, the practical signal is availability. Monitor the radsecproxy service and the port it listens on, and alert on unexpected restarts or crashes in the system journal. This read-only command shows the last seven days of radsecproxy log entries on systemd hosts, where repeated failures or restarts would stand out.

Review recent radsecproxy log entries (systemd hosts, read-only)Shell
journalctl -u radsecproxy --since "7 days ago"

If you also run public websites, uptime monitoring is a good habit for any service that others depend on.

This article will be incomplete until CVE identifiers and technical details are published. Check the Debian security tracker for updates rather than relying on third-party summaries.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6632-1] radsecproxy security updatelists.debian.org ·
  • Debian
  • radsecproxy
  • RADIUS
  • denial of service
  • DSA