Kali Linux 2023.4: Upgrade an Old Kali Install to 2026.2

Yes — a Kali Linux 2023.4 machine upgrades straight to the current release, Kali 2026.2, in one jump. There is no chain of in-between versions to install. Open a terminal and run three commands: first sudo wget https://archive.kali.org/archive-keyring.gpg -O /usr/share/keyrings/kali-archive-keyring.gpg, then sudo apt update, then sudo apt full-upgrade -y — and reboot when it finishes. The first command is the one nobody tells you about, and on a 2023.4 install it is not optional.

Here is the part that surprises almost everyone: your old Kali is not failing to update because it is broken, outdated, or compromised. In April 2025 the Kali team lost access to their own repository signing key and had to create a new one — so every single Kali machine installed before then, 2023.4 included, now refuses sudo apt update with "Missing key 827C8569F2518CC677FECA1AED65462EC8D5E4C5, which is needed to verify signature" until you install the replacement key by hand. That single fact explains the error you probably came here with, and the rest of this page explains everything around it.

The laptop that "got hacked" (it didn't)

Jake runs a small phone shop. In the back room there is an old ThinkPad running Kali Linux 2023.4 — he set it up from this very post's download links back in January 2024. He uses it maybe twice a month: checking a customer's Wi-Fi router settings, securely wiping drives on trade-in laptops before resale, the occasional recovery job.

Jake: "So last Saturday I finally ran the update thing, and it threw a wall of red text about a missing key and signatures. A signature error, on a hacking OS. I assumed someone had gotten into it. A repair guy quoted me $40 to wipe it and reinstall, and I nearly paid him, because I had a $60 drive-wipe job waiting on that machine."

Ethan: "You almost paid $40 to fix a machine that wasn't broken. Nothing on your laptop failed. Kali — the project itself — lost the key it used to sign its software back in April 2025, and made a new one. Your laptop still carries the old key, so it looks at the new signatures and says: I can't verify this, I refuse. That refusal is apt doing its job correctly."

Jake: "Its job being what, exactly?"

Ethan: "Think of your shop's supplier. Every parts shipment arrives with a seal so you know it really came from them and nobody swapped the box in transit. One day the supplier's sealing stamp is destroyed, so they start using a new stamp — and until they hand you a sample of the new seal, you'd reject every genuine shipment as suspicious. That's your laptop right now. The fix is one command: download the new seal. Then it updates like nothing ever happened."

That is the whole story of this page in miniature. The one-command fix is above in the Quick Answer. Everything below is what changed between 2023.4 and today, in order, so that every error you might hit on the way up makes sense — plus the answer for the smaller group of readers who came here wanting the old 2023.4 ISO on purpose, which has its own section, because the download links this post originally carried are now dead.

Why there is no "upgrade path" — and why that saves you

If you come from Windows, being "ten versions behind" sounds like a long staircase: install 2024.1, then 2024.2, then 2024.3, and so on until you reach 2026.2. Roughly ten numbered Kali releases have shipped since 2023.4, so people reasonably brace for ten upgrades.

Kali does not work that way. It is a rolling distribution: there is one continuously updated stream of packages, called kali-rolling, and every machine points at it. The version numbers you see — 2023.4, 2024.2, 2026.2 — are snapshots of that stream, taken roughly four times a year and pressed into installer images for new machines.

Ethan: "The releases are photographs of a river. The river moved on; the photographs didn't. When you upgrade, you're not climbing from photo to photo — you're stepping back into the river at today's water level. One step, whether you left in 2023 or last month."

Jake: "Then why does Kali bother with version numbers at all?"

Ethan: "For people installing fresh. A dated ISO tells you what you're downloading, gives the team a marketing moment for new tools, and gives documentation something to refer to. But an installed machine only ever knows one destination: current. That's why the upgrade command has no version in it."

This is genuinely good news for you. It means the two-and-a-half-year jump from 2023.4 to 2026.2 is one sudo apt full-upgrade, not ten. The download is bigger and the risk of a hiccup is a little higher than a routine monthly update — that is what the failure section below is for — but the procedure is identical.

One lane-marker before we start, so you land on the right page of this site: this article is for machines that are years behind, and for finding old ISOs. If you just want the current release's download links and what's new in it, that is the Kali 2025.3 release post, and the complete beginner's guide to getting Kali covers a fresh install from zero.

What changed between 2023.4 and 2026.2, in order

You do not need this history to run the upgrade. You need it to understand the errors the upgrade might show you, and to judge whether that old install in your cupboard is still trustworthy. Four dates matter.

December 2023 — Kali 2023.4, where this post began

Kali 2023.4 shipped in December 2023 with GNOME 45 as its headline desktop option and a batch of new tools — cabby, exiflooter, h8mail, ReconSpider among them. The original version of this article was a short download-and-upgrade note for that release, and for a few months it was exactly what people needed. Everything else on this page exists because of what happened to that release's world afterwards.

Late March 2024 — the xz-utils backdoor scare

A few months later, a backdoor was discovered in the xz-utils compression library — CVE-2024-3094, one of the most serious supply-chain incidents Linux has seen. Because Kali is rolling, machines that updated during a short window in late March 2024 briefly received the affected version before Kali pushed the fix. A machine sitting on stock 2023.4 that never updated was actually not exposed to that one — a rare case where being lazy about updates helped. If you did update in that window and never checked, our Kali 2024.2 post explains how to check whether you were affected.

April 2025 — Kali loses its signing key (the part that breaks your machine)

This is the big one, and it deserves a proper explanation because the error it causes looks scary and the cause sounds almost unbelievable.

Every package Kali publishes is cryptographically signed, and your machine keeps the matching public key in a small file called a keyring — literally a ring of trusted keys, stored at /usr/share/keyrings/kali-archive-keyring.gpg. When apt update runs, it checks the repository's signature against that keyring before trusting anything.

In April 2025, the Kali team announced they had lost access to their repository signing key. Not stolen, not compromised — lost. They froze the repository (from Friday, April 18, 2025), generated a fresh key, and re-signed everything with it. The new key's fingerprint is 827C 8569 F251 8CC6 77FE CA1A ED65 462E C8D5 E4C5, replacing the old ED444FF07D8D0BF6.

The consequence: a new key cannot announce itself through the very channel it signs. Every Kali installed before the switch — every 2023.4, 2024.x, and early-2025 machine on Earth — fails its next apt update with:

Missing key 827C8569F2518CC677FECA1AED65462EC8D5E4C5, which is needed to verify signature.

And every one of them is fixed the same way, by fetching the new keyring over plain HTTPS:

sudo wget https://archive.kali.org/archive-keyring.gpg -O /usr/share/keyrings/kali-archive-keyring.gpg

2025 — signature checking gets stricter

Around the same period, Kali's apt moved to a stricter, modern signature verifier called sqv (from the Sequoia-PGP project). Two practical effects for you. First, signature problems on newer installs show up as "Sub-process /usr/bin/sqv returned an error code" rather than the classic gpg wording — different costume, same category of problem, same keyring fix. Second, sqv is strict about key expiry dates: Kali's keys carry expiry dates that get extended periodically, so even a healthy install that sleeps in a drawer for a year can wake up to a signature error simply because its copy of the key expired. Once again: refresh the keyring file, and it clears.

2026 — a faster Kali, a new sources format, kernel 6.19

The current release, Kali 2026.2 (end of June 2026), is what your upgrade lands on. Compared with your 2023.4 desktop it is a different machine: Linux kernel 6.19 (Kali deliberately skipped kernel 7.0 to keep NVIDIA driver builds working), Xfce as the default desktop with GNOME 50 and KDE Plasma 6.6 as options, about nine new tools including arsenal-ng and legba, a trimmed ~60 MB initrd, and noticeably faster boot in virtual machines. Under the hood, fresh installs now define their repositories in a new file format called DEB822, at /etc/apt/sources.list.d/kali.sources, instead of the classic one-line /etc/apt/sources.list. Your upgraded machine keeps its old-style line, and it keeps working — do not feel obliged to convert it.

August 2026 — the old download links quietly died

One more change, and it is a correction to this very page. The original version of this post carried direct links to cdimage.kali.org/kali-2023.4/. Those links are dead: as of August 2026 that mirror carries only kali-2026.1, kali-2026.2, current, and weekly builds. Old releases move to a separate archive server — full details in the old-ISO section if that is what you came for.

The upgrade, step by step — from 2023.4 or any old Kali

The whole thing is six small steps. On a decent connection, budget 30–90 minutes, most of it unattended downloading. Plug a laptop into power first — a battery death mid-upgrade is the one self-inflicted wound this process allows.

Step 0 — confirm what you are actually running

Open a terminal (press Ctrl + Alt + T) and run grep VERSION /etc/os-release. Whatever number it prints — 2023.4, 2022.1, anything — the steps below are the same. If that command feels unfamiliar, the checking-your-Kali-version guide walks through it gently. Also check free disk space with df -h / — you want at least 8–10 GB free for a jump this large, since apt downloads the packages before it installs them.

Step 1 — install the new archive keyring

Required on anything installed before April 2025; harmless on anything newer, so when in doubt, run it:

sudo wget https://archive.kali.org/archive-keyring.gpg -O /usr/share/keyrings/kali-archive-keyring.gpg

Plain English: wget downloads a file; -O tells it exactly where to save it, overwriting the stale keyring in place; sudo runs it with administrator rights, because that folder belongs to the system. It finishes in a second and prints a short saved-file summary.

Step 2 — check your sources line

Run cat /etc/apt/sources.list. On a healthy old install you should see one active line:

deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware

The word that matters is kali-rolling — that is the river from earlier, and it is why no version number appears anywhere in this upgrade. If your line says something else (a mirror URL is fine; a branch like kali-last-snapshot is deliberate-conservative; anything mentioning an old codename is a problem), fix it to match the line above with sudo nano /etc/apt/sources.list, then save with Ctrl + O and exit with Ctrl + X.

Step 3 — run the upgrade

sudo apt update && sudo apt full-upgrade -y

Three things worth knowing about that line. apt update refreshes the list of what exists — it installs nothing. full-upgrade (rather than plain upgrade) is the correct verb for a jump this size: it is allowed to remove or replace packages when the last two-plus years of changes demand it, which plain upgrade is not — plain upgrade would leave you half-migrated. And -y pre-answers the "do you want to continue?" question so the download can start unattended. Expect apt to announce a couple of thousand upgraded packages and a download in the 2–3 GB range. Let it run.

Step 4 — answer the prompts sensibly

A jump across years will pause you two or three times mid-install. The two prompts you will actually meet:

"A new version of configuration file X is available... keep your currently-installed version?" — if you never hand-edited that file (for most people, that is every file), take the package maintainer's new version. If it is a file you customized and care about, keep yours. When you have no idea, the safe default apt highlights is fine — that is what it is for.

"Restart services during package upgrades without asking?" — Yes. On a desktop or lab machine there is nothing running that a service restart can hurt.

Step 5 — reboot and verify

Run sudo reboot. A big upgrade replaces the kernel — the core of the operating system — and the new one only takes over on the next boot. After logging back in, run grep VERSION /etc/os-release again: it should now say 2026.2. Finish with sudo apt autoremove -y to sweep out packages the old system needed and the new one does not — after a multi-year jump this routinely frees a gigabyte or more.

When the upgrade fails: symptom by symptom

Big jumps hit turbulence more often than monthly updates. Every symptom below has a named cause and a fix — none of them means starting over.

"Missing key 827C8569F2518CC677FECA1AED65462EC8D5E4C5"

The April 2025 key replacement, exactly as described in the timeline. Your install predates the new key. Run the keyring command from Step 1, then sudo apt update again. This clears it in one shot.

"Sub-process /usr/bin/sqv returned an error code"

The stricter signature checker rejecting what your machine holds — most often because the key on disk has passed its expiry date while the machine sat unused. Same fix: re-fetch the keyring (Step 1), update again. If it persists, your system clock being wildly wrong can also fail signature date checks — set the date correctly and retry.

"dpkg was interrupted, you must manually run 'dpkg --configure -a'"

The upgrade was cut off mid-flight — closed lid, power cut, impatient Ctrl+C — and the package system is holding a half-finished transaction. Run sudo dpkg --configure -a to let it finish what it started, then resume with sudo apt full-upgrade -y. The dedicated dpkg-was-interrupted guide covers the stubborn variants, including lock files that refuse to release.

"Unmet dependencies" or "held broken packages"

Some package versions on your old system conflict with what current Kali wants — common when third-party tools were installed outside apt years ago. Run sudo apt --fix-broken install, then retry the full-upgrade. If one specific package keeps blocking, removing it (sudo apt remove packagename), upgrading, and reinstalling it afterwards is quicker than fighting it.

The disk filled up mid-upgrade

Apt stores every downloaded package before installing, so a multi-gigabyte jump can choke a small disk. Run sudo apt clean to empty the download cache, sudo apt autoremove -y to drop obsolete packages, check with df -h /, and resume. This is also the honest signal that a shop machine deserves a bigger SSD — Jake's ThinkPad runs on a 128 GB drive, and this upgrade is the closest it has come to filling it.

The terminal looks wrong after the upgrade

If your shell, prompt, or theme behaves oddly post-upgrade, it is usually the shell configuration lagging the new defaults — Kali switched its default shell to Zsh in 2020, and machines carried across big upgrades sometimes land with mismatched configs. The Zsh-missing-after-upgrade fix still applies. Desktop looks different? That is not a bug — 2026.2 defaults to Xfce, and if you miss GNOME the install-GNOME-as-default guide brings it back in ten minutes.

If you genuinely need the old Kali 2023.4 ISO

A steady trickle of readers lands on this page wanting the opposite of an upgrade: the actual 2023.4 image, on purpose. Legitimate reasons exist — a training course or certification lab pinned to that release, reproducing a writeup or CTF exactly as published, or testing how a tool behaved before a later change. If that is you, here is the honest state of things.

Where the 2023.4 ISO actually lives now

Not where this post originally pointed. The cdimage mirror drops old releases, and the direct 2023.4 links published here in 2024 are dead. Kali's permanent archive lives at old.kali.org/kali-images/, which keeps a folder for every release going back to the beginning — including kali-2023.4/ with the same installer images this post once linked directly. That is the only source you should use: never a torrent from a random site, and never, ever a paid download — anyone charging money for a Kali ISO of any age is running a scam, full stop. Kali is free and always has been.

Verify the checksum before you boot it

Old file, long journey, more chances for corruption or tampering — so verifying matters even more than it does for a fresh release. For the record, the SHA256 checksum for the 2023.4 amd64 installer as published at release was 49f6826e302659378ff0b18eda28121dad7eeab4da3b8d171df034da4996a75e — compare it against the sums file in the same archive folder. If you have never verified a checksum, the verify-a-Kali-download-on-Windows guide does it with nothing but built-in Windows commands.

The safe way to run an old Kali

Install it in a virtual machine, take a snapshot immediately after setup, keep it off the internet except when the lab task demands it, and roll back to the snapshot when done. That gives you the frozen-in-time environment your course or writeup expects, without an aging OS accumulating exposure on real hardware. When the pinned task is finished, delete it — your long-term machine should be the upgraded one.

Jake: "Honest question — my 2023.4 was working fine before this key thing. Why not just skip all of it and keep using it as-is, no updates?"

Ethan: "Because of what that laptop does. It touches customers' routers and handles trade-in drives. A frozen security toolkit ages in reverse — every month, more of its tools have known holes and more of its checks miss things that changed. For a machine that only ever plays old CTFs offline, sure, freeze it. For the one earning money in your shop? Twenty minutes of upgrade is the cheapest insurance you'll buy this year."

After the upgrade: five minutes of housekeeping

Three quick wins while the terminal is still open. First, if you use Metasploit, refresh it and rebuild its database — the update-Metasploit guide takes two minutes and saves a confusing session later. Second, set a reminder to run sudo apt update && sudo apt full-upgrade -y monthly — small regular sips are painless, and you will never need this page's long-jump instructions again. Third, your newly current Kali can do things the 2023.4 one never could: it will happily run a modern local AI model, fully offline — the Gemma 4 on Kali guide is a fun first errand for the new kernel.

FAQ

Can I upgrade Kali 2023.4 directly to 2026.2 without installing every version in between?

Yes. Kali is a rolling distribution, so one sudo apt full-upgrade takes any old install straight to current. The only extra step for pre-April-2025 installs is refreshing the signing keyring first.

Why does sudo apt update fail with a missing key error on my old Kali?

Kali lost access to its repository signing key in April 2025 and replaced it. Installs from before then carry only the old key, so they cannot verify current packages. Download the new keyring with the wget command in Step 1 and the error clears permanently.

Is Kali Linux 2023.4 still safe to use in 2026?

Offline in a virtual machine for a pinned lab task, yes. As a working security machine, no — its tools are years behind and vulnerabilities patched since 2023 remain open on it. Upgrade any machine that does real work.

Where can I download the Kali Linux 2023.4 ISO now?

From Kali's official archive at old.kali.org/kali-images/, in the kali-2023.4 folder. The direct cdimage.kali.org links that circulated in 2024 (including in the original version of this post) are dead — that mirror now keeps only recent releases.

Is it better to reinstall Kali instead of upgrading an old version?

For 2023.4 and anything from 2020 onwards, upgrading is the better default — it keeps your files and settings and takes one command. Reinstall only for pre-2020 installs, a corrupted package system, or a disk too small for the upgrade download.

How long does the upgrade from an old Kali take?

Typically 30 to 90 minutes: a 2–3 GB download plus installation of a couple of thousand packages. Connection speed dominates. Keep the machine on power and let it run unattended after answering the first prompts.

Will upgrading delete my files and tools?

No. Your home folder, documents, and configurations survive. full-upgrade may remove obsolete packages that conflict with current ones, and it lists exactly what before proceeding. A backup before any multi-year jump is still sensible practice.

Do I need to run sudo apt update before sudo apt full-upgrade?

Yes — update refreshes the catalog of available packages; full-upgrade acts on that catalog. Running full-upgrade against a stale catalog upgrades you to wherever the catalog last pointed, not to current. Chain them with && and it is one line anyway.

Is Kali Linux still free, or do I have to pay for 2026.2?

Completely free, every version, forever — downloads, upgrades, and all included tools. Anyone asking for payment for a Kali ISO or a "license" is a scammer. The only real costs are your bandwidth and hardware.

Is it legal to install and use Kali Linux?

Yes — it is just an operating system. What is regulated is how you use its tools: testing systems you own or have written permission to test is fine; pointing them at anything else can be a crime in most countries. The OS is legal; unauthorized use of it is not.

What is the default username and password in Kali Linux?

On live and pre-built images: username kali, password kali. There is no root login by default — that ended in 2020 — so administrative commands go through sudo. Change the default password on anything that stays installed.

What is the latest version of Kali Linux right now?

Kali Linux 2026.2, released at the end of June 2026, with Linux kernel 6.19 and Xfce as the default desktop. Kali ships roughly four numbered releases a year, but an installed machine just follows kali-rolling and picks them up automatically.

Revision note. Originally published January 4, 2024 as a short download-and-upgrade note for the then-new Kali 2023.4. Rewritten August 10, 2026: the direct 2023.4 download links from the original are dead and now point to Kali's permanent archive instead, and the page now covers what the original could not have known — the April 2025 signing-key loss that breaks apt on every install of that era. If you landed here after that error made you think you had been hacked, or that you had somehow ruined your install: you had not, and you were in very good company — half the Kali world hit the same wall the same week. Corrections and stubborn cases are always welcome through the contact page. Happy upgrading, and may your next one be a boring one.