Maintenance After Debian 11

Maintenance After Debian 11

At a glance

From 1 September 2026, Robustel does the security work Debian used to do.

Who fixes what, how fast, until when
The kernel does not change within 2.x. Installed devices can stay on 2.x.

Debian's own support for Debian 11 ended on 31 August 2026. RobustOS Pro 2.x and MG Core 2.x are built on Debian 11, and Robustel committed at launch to a ten-year maintenance life for them. That commitment stands: Robustel maintains both 2.x lines through 2031. From 1 September 2026, Robustel has taken over the security maintenance that Debian used to provide.

At a glance
Maintained through 2031. Critical and High vulnerabilities fixed on published deadlines. Fixes arrive as individual security update packages from the Robustel website or RCMS. The kernel does not change within 2.x. Installed devices can stay on 2.x.

What is maintained, to 2031

Critical and High vulnerabilities and critical bugs are fixed. New features go into 3.x.

Critical vulnerabilities
Assessed within 3 days.
Fixed within 14 days
High vulnerabilities
Assessed within 5 days.
Fixed within 30 days
Critical bugs
System crash or hang, loss of major functionality.
Fixed
Medium and low
Mitigation advice where the risk warrants it.
Case by case
New features, general bug fixes
These go into the 3.x generation.
Not in 2.x
Actively exploited
Prioritized regardless of score. Severity is classified using CVSS.
Comes first
MaintainedHow
Critical-severity vulnerabilitiesYesAssessed within 3 days, fixed within 14 days
High-severity vulnerabilitiesYesAssessed within 5 days, fixed within 30 days
Critical bugs (system crash or hang, loss of major functionality)YesFixed
Medium- and low-severity vulnerabilitiesAssessed case by caseNo committed fix; mitigation advice where the risk warrants it
New features, general bug fixesNoThese go into the 3.x generation

Severity is classified using CVSS (first.org/cvss). Vulnerabilities that are actively exploited are prioritized regardless of score.

How each vulnerability is handled

The question is whether it can actually be reached and exploited on the gateway, not the generic score.

Fix
A real attack path: a security update package within the deadline.
Mitigate
Configuration, access control or network isolation removes the risk: Robustel publishes the recommended configuration.
Not affected
The vulnerable code is not present or cannot be triggered: an assessment note.
How a fix reaches your device

Every published Critical or High vulnerability affecting the software in the firmware image is assessed by Robustel's Product Security Incident Response Team (PSIRT). The assessment asks whether the vulnerability can actually be reached and exploited on a RobustOS Pro or MG Core gateway, rather than acting on the generic score alone. It ends in one of three outcomes:

1
Fix
Where there is a real attack path, a security update package is released within the deadline.
2
Mitigate
Where configuration, access control or network isolation removes the risk, Robustel publishes the recommended configuration.
3
Not affected
Where the vulnerable code is not present or cannot be triggered, Robustel issues an assessment note.
The three outcomes of a vulnerability assessment.

The kernel stays the same across 2.x

Security fixes are backported into the 2.x kernel through 2031. A newer kernel arrives with 3.x.

Same kernel version
Not changed within a major release.
Fixes backported
Why
A newer kernel would change behaviour your applications, and the certifications, rely on.

Robustel does not change the Linux kernel version within a major release. Moving to a newer kernel would require full regression testing of every application above it and would change behaviour that your applications, and the product's certifications, rely on. Instead, security fixes for the kernel are backported into the 2.x kernel through 2031. A newer kernel arrives with the 3.x generation.

How you get security updates

Individual security update packages, not full firmware releases.

Download the package for your model, install it through the local upgrade or package page, reboot, confirm the version.
Through RCMS
Send the deployment task, batched if you like. RCMS pushes, installs, reboots and reports per device.
Keep 2.x devices connected to RCMS, or check the Robustel website regularly, so Critical and High updates are installed within their deadlines.

Security fixes are released as individual security update packages, not as full firmware releases. You fix the affected software without waiting for, or performing, a full firmware upgrade.

From the Robustel website

  1. Log in to the software download area and find the security update package for your model.
  2. Download it to your computer or to storage on the device.
  3. Install it through the device's local upgrade or package management page.
  4. Reboot, then confirm the version and that the device runs normally.

Through RCMS

  1. Make sure the devices are connected to RCMS and online.
  2. Select the security update package and send the deployment task to the devices; tasks can be batched.
  3. RCMS pushes, installs and reboots, and reports the result for each device.
  4. Follow progress and results for the whole fleet in RCMS.

Recommendation: keep 2.x devices connected to RCMS, or check the Robustel website regularly for security update announcements, so that Critical and High updates are installed within their deadlines.

apt and the Debian 11 repositories

apt update and apt install still work. The Debian 11 repositories just receive no new fixes.

Repositories stay online
Default configuration works on 2.x devices.
apt works
Security fixes
From Robustel's security update packages, not from apt.
Not affected by apt
Third-party repositories
Packages from outside Robustel's image are not covered.
Don't use them

If apt update fails, two cases are known:

"Release file expired"
A temporary state of Debian's repository. To update in the meantime:
sudo apt-get -o Acquire::Check-Valid-Until=false update
"404 Not Found" for deb.debian.org
Debian 11 has moved to its archive server. In /etc/apt/sources.list, change deb.debian.org to archive.debian.org in each Debian line that fails. Leave the Robustel lines as they are.

Debian's official support for Debian 11 has ended, but its repositories remain online: apt update and apt install work on 2.x devices with their default configuration. What has changed is that the Debian 11 repositories receive no new fixes — new security fixes come from Robustel's security update packages, through the Robustel website and RCMS.

  • If apt update failed in early September 2026: that was a temporary state of Debian's security repository, resolved by Debian on 12 September 2026. No change on the device is needed.
  • RobustOS Pro 2.5.1 and MG Core 2.1.11 / 12.1.1 include a fix for apt command failures. Install them from the Robustel website or through RCMS once released.
  • When Debian moves Debian 11 to its archive server, the default repository address will stop working. Security fixes are not affected: they come from Robustel's security update packages, through the Robustel website and RCMS.
  • Do not point devices at third-party package repositories. Packages from outside Robustel's image are not covered by Robustel's maintenance.

If apt update fails

Two cases are known. Neither affects security fixes, which come from Robustel's security update packages through the Robustel website and RCMS.

  1. The error says a Release file has expired (“invalid since …”). This is a temporary state of Debian's repository, as in early September 2026, and Debian normally corrects it. To update in the meantime, run:
    sudo apt-get -o Acquire::Check-Valid-Until=false update
  2. The error says 404 Not Found for deb.debian.org. Debian has moved Debian 11 to its archive server. In /etc/apt/sources.list, change deb.debian.org to archive.debian.org in each Debian line that fails, then run sudo apt update. Leave the Robustel lines (debian.robustel.net) as they are. The archive holds the last Debian 11 packages and receives no new fixes.

The next generation: 3.x

Debian 13 with Linux kernel 6.12, back on Debian's official long-term-support track. Dates are current expectations.

ReleaseWhen and which models
RobustOS Pro 3.0Expected end of 2026 · EG5100, EG5101, EG5120, EG5200
RobustOS Pro 3.1To be announced · adds EG3120, EV8100, LG3120, LG5120, R1520LG
MG Core 3.0Expected end of 2027 · MG460 Gateway and MG460 Forwarder expected
3.x is expected to be maintained through 2035. The 2.x commitment to 2031 is not affected.

Both product lines move to Debian 13 with Linux kernel 6.12, which puts them back on Debian's official long-term-support track. The dates below are Robustel's current expectations.

ProductBaseExpected releaseModels
RobustOS Pro 3.0Debian 13, kernel 6.12End of 2026EG5100, EG5101, EG5120, EG5200
RobustOS Pro 3.1Debian 13, kernel 6.12To be announcedAdds EG3120, EV8100, LG3120, LG5120, R1520LG
MG Core 3.0Debian 13, kernel 6.12End of 2027MG460 Gateway and MG460 Forwarder expected

Each major version carries the same ten-year maintenance life: the 3.x generation is expected to be maintained through 2035. The 2.x commitment to 2031 is not affected by the 3.x releases.

Stay on 2.x or move to 3.x

Installed devices: stay on 2.x. New projects: can start on 3.x.

Installed devices
Maintenance through 2031 covers them. Plan a migration as your projects require.
Stay on 2.x
New projects
Start validation on 3.x now if it suits your timeline; use the generally available release for production.
Can start on 3.x
Moving from 2.x to 3.x is a reflash, not an update. It erases the configuration and your application data.
1
Check the model
Is it in the 3.x plan?
2
Test on Debian 13
Some applications need changes or a rebuild.
3
Configuration and application data.
4
Flash, restore, verify
Then return the device to production.

Installed devices: stay on 2.x. Maintenance through 2031 covers them, with Critical and High fixes delivered as above. There is no need to rush a migration; plan it as your projects require.

New projects: can start on 3.x. Start validation on 3.x now if it suits your timeline, and use the generally available release for production.

Before you move a device
Moving from 2.x to 3.x is a reflash, not an update — it erases the configuration and your application data.
1
Check the model
Confirm it is in the 3.x plan above.
2
Test your own applications on Debian 13
Scripts, libraries and dependencies change between Debian generations; some applications need changes or a rebuild.
3
Export the configuration and your application data — reflashing erases both.
4
Flash, restore, verify
Flash the 3.x image, restore the configuration, redeploy and verify your applications, then return the device to production.
Moving a device from 2.x to 3.x.

Report suspected vulnerabilities through the Robustel Security Centre (robustel.com/security-centre).

Reporting a vulnerability

Report suspected vulnerabilities through the Robustel Security Centre (robustel.com/security-centre).

Related documents

Next · step 13 of 13End of life →Support windows, decommissioning and handing devices over.