Turning on the Ubuntu Pro Edge archive puts AI-built security patches on your machine before a human has qualified them. That is the deal Canonical offers: fixes for known CVEs produced by its Surge pipeline, delivered before they pass qualification and reach the regular -security pocket, in exchange for you accepting the risk of an unqualified build. It is opt-in, and you should treat it as a change to your trust model, not a routine repository add.
This guide covers what pro-enable-edge actually writes to /etc/apt, how to see which installed packages Edge can replace, how to take a single fix and roll it back, and the opt-out that leaves nothing behind. Two of those steps do not behave the way the documentation suggests, and we show both. Every command ran on 15 November 2026 on Ubuntu 26.04.1 LTS and 24.04.5 LTS, attached to Ubuntu Pro with the stock -security pocket left in place, so manual mode never weakens the default update path.
What the Edge archive ships, and who has checked it
An Edge package has passed an automated build and test pipeline, not the full qualification Canonical’s security team applies to -security. According to the Canonical announcement, Surge is a multi-agent system that takes a known CVE, studies the upstream fix, has competing models write backports, judges them by consensus and routes edge cases, low-confidence scores and deadlocked votes to security engineers. The same post states that updates in the traditional channels stay strictly human-validated, and the kernel is not part of Surge at all.
So one machine ends up with three pockets and three different levels of review, and apt decides between them only by pin priority. Because the pin is the whole control, it’s worth knowing each value before you enable anything. Here they are side by side as they behaved in the lab.
| Who validates the fix | Default apt pin | Installed by unattended-upgrades | |
|---|---|---|---|
Ubuntu archive -security | Canonical security team, human-reviewed | 500 | Yes |
| ESM infra and apps | Canonical security team, human-reviewed | 510 | Yes, when attached |
| Edge (manual mode) | Surge pipeline, no qualification yet | 490 | No, the pin keeps it out |
Edge (--automatic-updates) | Surge pipeline, no qualification yet | 510 | Yes |
Scope is narrow. The Canonical how-to limits Edge to LTS releases from 18.04 through 26.04, with ESM Infra or ESM Apps enabled, so interim releases get nothing. Kernel CVEs still arrive through the normal SRU cycle and its -proposed testing, which means Edge can change your userspace libraries but never the kernel you boot.
An attached Ubuntu Pro subscription
Edge is invisible until the machine is attached to Ubuntu Pro, because the pro-edge package itself lives in the ESM infra pocket. On an unattached 26.04 VM, apt-cache policy pro-edge printed nothing at all. Pro is free for personal use on up to five machines; grab the token from your Ubuntu Pro dashboard and attach:
sudo pro attach YOUR_PRO_TOKEN
A mistyped or revoked token fails fast and leaves the machine unattached. This is the exact error from our unattached VM:
Invalid token. See https://ubuntu.com/pro/dashboard
Our two lab VMs came from Ubuntu Pro cloud images, which attach themselves at first boot, so no personal token was involved. Either route ends in the same entitlements. Confirm that esm-infra or esm-apps reads enabled before going further:
sudo pro status
Both ESM services showed as enabled on 26.04, with Livepatch on as well. If either reads disabled, run sudo pro enable esm-infra first, because the Edge sources reuse the ESM keyrings and credentials. Account and subscription lines are redacted here.

If you’re still building the machine itself, our Ubuntu 26.04 install walkthrough gets you to this point, and the lab-tested Ubuntu Desktop 26.04 guide carries on through Chrome, Node.js, Java, Docker and KVM on a desktop you’ll keep patched.
Edge access through the pro-edge package
Enabling Edge is not a pro enable service. It is a small package that ships two scripts, and one of them rewrites your apt configuration. Install it, then run the enable script:
sudo apt-get install -y pro-edge
sudo pro-enable-edge
In the capture, the package comes from esm.ubuntu.com/infra at pin 510, installs two scripts under /usr/sbin, and the enable step reports four files. Write those paths down. The opt-out later depends on all four disappearing, and nothing in pro status will remind you they exist.

Its only option is --automatic-updates, printed in the usage line as Usage: /usr/sbin/pro-enable-edge [--automatic-updates]. Without it you get manual mode, which is where you should start, since every Edge install then needs a deliberate version pin from you.
Four apt files and a 490 pin
What keeps manual mode safe is one number. The script adds three deb822 repositories (edge, infra-edge and apps-edge) to /etc/apt/sources.list.d/ubuntu-edge.sources, signed with the existing ESM keyrings, and pins all three origins at 490. That sits below the archive’s 500, so apt never prefers an Edge build on its own. Read the files yourself:
cat /etc/apt/sources.list.d/ubuntu-edge.sources
cat /etc/apt/preferences.d/ubuntu-edge
cat /etc/apt/apt.conf.d/90ubuntu-edge
Each file has one job, and you should be able to confirm all four on any host you audit:
ubuntu-edge.sourceslists the edge, infra-edge and apps-edge repositories withSigned-Bypointing at an ESM keyring.preferences.d/ubuntu-edgepinso=UbuntuEdge,o=UbuntuESMEdgeando=UbuntuESMAppsEdgeat 490.apt.conf.d/90ubuntu-edgeadds the three Edge origins to unattended-upgrades.auth.conf.d/90ubuntu-edgeholds the Edge credentials at mode 0600.
Watch the third file most closely. Even in manual mode it adds the three Edge origins to Unattended-Upgrade::Allowed-Origins, so unattended-upgrades is already permitted to install Edge packages and only the 490 pin stops it.

Anyone who edits that preferences file, or a configuration tool that drops its own Pin-Priority: 500 rule on o=UbuntuEdge, silently turns manual mode into automatic. The fourth file, /etc/apt/auth.conf.d/90ubuntu-edge, holds your Pro credentials for the Edge hosts at mode 0600; keep it out of config backups you share.
Package origin checks that work in manual mode
The documented way to list Edge updates is apt list --upgradable '?origin(^Ubuntu.*Edge$)'. In manual mode it returned an empty list on both releases, even though Edge carried fixes for installed packages. The reason is the pin: an Edge build at 490 never becomes the candidate, so apt does not count it as upgradable. Ask apt for installed packages that have any Edge version instead:
apt list '?and(?installed,?any-version(?origin(^Ubuntu.*Edge$)))'
apt policy python3-jwt
On 26.04 the first query found three installed packages that Edge can replace. For one of them, apt policy shows the ~surge1 build from resolute-edge-security at 490. The installed version outranks it at 500, served by both -updates and -security at 500, so the candidate stays on the reviewed build.

Do not expect the Pro client to tell you any of this. pro status --all has no Edge row (a grep for “edge” exited 1), and pro security-status counts only esm-infra and esm-apps. The one security update it reported receiving on 26.04 was pro-edge itself. To see which pocket a version comes from, apt show -a prints an APT-Sources line per version:
sudo pro security-status
apt show -a python3-jwt 2>/dev/null | grep -E "^(Version|APT-Sources):"
Only the Edge build lists esm.ubuntu.com/edge as its source, which makes this the fastest audit for a single package. Security-status gave no hint that Edge was configured at all.

Our apt cheat sheet has more pattern queries in the same ?origin() style if you want to build fleet reports around them.
Edge packages on 26.04 and 24.04
Edge is small and moves fast, so treat this as a dated snapshot from 15 November 2026 rather than a fixed list. Index sizes told the story before any query did: on 26.04 the three Edge indexes were 5987 B, 652 B and 10.6 kB, while 24.04’s edge pocket alone was 28.7 kB.
| Release | Edge pocket (examples) | Apps-edge pocket (examples) | Installed packages Edge can replace |
|---|---|---|---|
| Ubuntu 26.04 LTS | python3-jwt, python3-mako, python3-setuptools, libjxl, hello | etcd, iperf3, python3-anyio, python3-fsspec, golang-golang-x-crypto-dev | 3 (python3-jwt, python3-setuptools, python3-pkg-resources) |
| Ubuntu 24.04 LTS | util-linux family, cups, elfutils, libbpf, harfbuzz, alsa-lib, gst-plugins-base | freerdp2, icinga2, python3-pip, libnetty-java, retroarch, iperf3 | 19 (util-linux, mount, fdisk, libbpf1, elfutils libraries, python3-jwt, python3-oauthlib) |
Risk differs a lot between the two. On 26.04 Edge touched a few Python libraries; on a default 24.04 cloud image it offered replacements for the util-linux family, which every boot depends on, so a bad build there costs far more than a broken JWT library. The infra-edge pocket held only the hello test package on both releases. If you’re weighing the two LTS lines for other reasons, our Ubuntu 26.04 feature rundown covers what changed.
A single Edge fix, installed and rolled back
Manual mode means you choose each build. Pin the exact version from apt policy; a bare apt install python3-jwt does nothing because the archive build is still the candidate:
sudo apt-get install -y python3-jwt=2.10.1-4ubuntu1.4~surge1
Before trusting it, read what it claims to fix. apt changelog printed nothing for the Edge build on either release, so go to the copy the package installs:
zcat /usr/share/doc/python3-jwt/changelog.Debian.gz | head -9
Its top entry names CVE-2026-102269 and the patch file, and the maintainer line reads Unknown Maintainer, a clear marker that no person signed off this upload. Further down the same file, past the head cut, the human-reviewed -security entry carries a named maintainer. A final dpkg --compare-versions in the capture proves the ~surge1 suffix sorts below the final version.

Version ordering is the safety net. When the qualified fix lands in -security without the suffix, it outranks the Surge build and a normal upgrade replaces it. If the Edge build breaks something before then, downgrade to the archive version you noted earlier:
sudo apt-get install -y --allow-downgrades python3-jwt=2.10.1-4ubuntu1.3
Rolling back worked on both releases, and apt policy showed the archive build installed again. Those version strings are the 26.04 ones; on 24.04 the lab used python3-jwt=2.7.0-1ubuntu0.5~surge1 to install and python3-jwt=2.7.0-1ubuntu0.4 to roll back, so always copy yours from apt policy. Record the archive version before every Edge install; dpkg -l will not remember it for you, and our dpkg cheat sheet lists the queries for doing that across a fleet.
Automatic Edge updates and the 510 pin
Automatic mode hands package selection to unattended-upgrades, so every Surge build for an installed package lands without anyone reading its changelog. We tested it on 24.04 by snapshotting /etc/apt, then running:
sudo pro-enable-edge --automatic-updates
Against the snapshot, the diff changed exactly one thing: the three pins went from 490 to 510, level with ESM and above the archive. The unattended-upgrades origins were already in place from manual mode, so the next nightly run installs Edge builds without any further change.

With the higher pin, the documented ?origin query finally returns results. On the 24.04 VM it listed 19 packages, most of them from util-linux and elfutils.

Keep automatic mode for test machines and disposable desktops where an early CVE fix is worth a broken library. On anything that serves users, stay in manual mode and pick builds by changelog.
An opt-out that leaves nothing behind
Removing the package is the obvious way out, and it does not work. Canonical’s how-to says nothing about opting out, so we tested it. After sudo apt-get purge -y pro-edge, all four files stayed in /etc/apt and apt-get update still fetched the three Edge indexes.

On the 24.04 box in automatic mode it was worse: the pin stayed at 510 and all 19 Edge upgrades were still offered after the purge, so unattended-upgrades would have kept installing them. A second trap waits in the disable script. Run without sudo (we tried pro-disable-edge --help), it cannot delete the files, prints “Permission denied” for each, and still ends with “Unconfigured Ubuntu Edge”. Do not trust that line on its own. Note too that the script has no help output: it ignored --help and went straight to deleting, so sudo pro-disable-edge --help really does disable Edge.
A clean opt-out runs in this order:
- Reinstall
pro-edgeif you already removed it, so the disable script exists. - Run
sudo pro-disable-edgeas root, never as your user. - Confirm no Edge file remains under
/etc/apt. - Refresh the index and check that no package still shows an Edge version.
- Remove
pro-edgelast.
As commands, with the checks in between:
sudo apt-get install -y pro-edge
sudo pro-disable-edge
sudo grep -ril edge /etc/apt/
sudo apt-get update
apt policy python3-jwt
sudo apt-get purge -y pro-edge
After the disable step, the grep came back empty on our cloud VMs (on a desktop with the Microsoft Edge browser repo, expect that file to match and ignore it), apt-get update printed no Edge lines and the version table listed only archive builds. Deleting the four files by hand with sudo rm gave the same clean state on 24.04, which is your fallback if the package is gone from the mirror.

Any Edge build you installed stays installed after the opt-out. Downgrade it with the --allow-downgrades command from the rollback section, or wait for the archive to ship the qualified version, which outranks it.
Bug reports for Surge fixes
A broken Edge build is exactly the feedback Canonical asked for. File it against the ubuntu-security-edge project on Launchpad, not the regular Ubuntu package, and include the full ~surge version string, the CVE from the changelog and the archive version that worked. If the issue is a regression that the real -security update could also carry, our walkthrough on patching an Apache CVE on Ubuntu shows how we verify a human-reviewed fix before rollout.
Edge archive audit checklist
Run these checks on any machine that has ever had Edge enabled, and again after config management touches /etc/apt:
- The machine is attached to Ubuntu Pro with esm-infra or esm-apps enabled, or Edge is absent entirely.
/etc/apt/preferences.d/ubuntu-edgepins every Edge origin at 490 unless the host is meant to run automatic mode.- No other preferences file raises
o=UbuntuEdge,o=UbuntuESMEdgeoro=UbuntuESMAppsEdgeto 500 or higher. /etc/apt/auth.conf.d/90ubuntu-edgeis mode 0600 and owned by root.- Every installed
~surgepackage has a recorded archive version to roll back to. - The changelog of each installed Edge build has been read and names the CVE it fixes.
- On a host that dropped Edge, none of the four Edge files exists and
apt-get updatefetches noesm.ubuntu.comedge index. - No production server runs
pro-enable-edge --automatic-updates.
If check 7 fails on a box where someone only ran apt purge pro-edge, Edge is still live there. Reinstall the package and run the disable script as root before you sign the machine off.