Sapphire Security Firmware Covers 8 RX 7000 Cards: Update Now [2026]

By Indie Kings | October 2, 2026

Updated October 2, 2026: Sapphire published security firmware for 8 RX 7000 cards spanning RX 7600 through RX 7900 XTX. The files have been available since September 16 and were spotted on October 2.

Image: AMD header art. Credit: AMD.

What Changed

Sapphire released family specific security firmware updaters for Radeon RX 7000 series graphics cards, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire listings via TechPowerUp. The report states that the files cover 8 models from RX 7600 through RX 7900 XTX and that each family has its own updater plus an install guide plus a PDF document.

The same report states that the packages have been available since September 16 and were spotted on October 2. That timeline matters because many owners check drivers often but check firmware rarely, so a quiet mid September firmware release can sit unnoticed for weeks while systems remain on older code.

The update is described as a joint AMD security finding with no technical details published, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp. In other words, owners are being asked to update for security reasons without a public explanation of the flaw, the attack path, or the severity score. That lack of detail is frustrating but it is also common for early hardware security disclosures where partners patch first and publish details later [NEEDS VERIFICATION].

This post treats only three facts as verified: the 8 card list, the September 16 availability with October 2 spotting, and the joint AMD security framing with no technical details. Everything else about install behavior, reboot needs, version numbers, performance impact, and exploitability is marked [NEEDS VERIFICATION] because Sapphire has not published a public security bulletin with those specifics in the cited report.

For context, Radeon RX 7000 is the RDNA 3 generation for desktop. It spans entry level 1080p cards such as RX 7600 and RX 7600 XT, the China focused RX 7650 GRE, midrange RX 7700 XT and RX 7800 XT, and high end RX 7900 GRE, RX 7900 XT, and RX 7900 XTX [NEEDS VERIFICATION]. Firmware in this stack controls low level board behavior such as initialization, memory training, power limits, fan response, and security functions, while the Adrenalin driver controls the Windows software layer. Updating one does not replace the other, so owners need both current firmware and current drivers.

The practical takeaway is simple. If you own a Sapphire RX 7000 card in the covered list, download only the updater that matches your exact card family, read the PDF first, and flash once. Do not use a 7900 XTX file on a 7900 XT. Do not use a 7600 file on a 7600 XT. Do not flash a Sapphire package on another vendor card [NEEDS VERIFICATION]. The sections below map the covered models, the gaps, and a careful five step process.

Search interest around this story will likely cluster around phrases such as Sapphire RX 7000 firmware update, RX 7900 XTX security firmware, RX 7800 XT firmware updater, RX 7700 XT firmware download, RX 7600 XT firmware flash guide, and AMD security firmware October 2026 [NEEDS VERIFICATION]. This article answers those queries directly with the verified card list, the verified timeline, and a conservative install checklist that respects the missing technical details.

One more scope note helps avoid confusion. This is a Sapphire board firmware release reported through Sapphire download listings, not a general AMD Adrenalin driver release and not a motherboard BIOS release [NEEDS VERIFICATION]. If you were waiting for a new Adrenalin version with game optimizations, this is a separate track. Keep your driver update routine as is, add this firmware check on top of it, and verify both after reboot.

Covered Cards

The verified coverage is 8 RX 7000 models: RX 7600, RX 7600 XT, RX 7650 GRE, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XT, and RX 7900 XTX, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp. Each family has a per family updater plus an install guide plus a PDF, which means owners should expect separate downloads rather than one universal tool.

The table below restates that verified list in a scannable form. Use it as a starting filter, then confirm your exact Sapphire submodel on the Sapphire download page before you download anything. Model names that look close can use different board designs, different memory setups, or different VBIOS branches [NEEDS VERIFICATION].

Coverage by segment tells a useful story. Entry level is covered with RX 7600, RX 7600 XT, and RX 7650 GRE. Midrange is covered with RX 7700 XT and RX 7800 XT. High end is covered with RX 7900 GRE, RX 7900 XT, and RX 7900 XTX. That is effectively the full mainstream RX 7000 desktop stack named in the report, which suggests a platform level security issue rather than a single board bug, although the exact cause remains undisclosed [NEEDS VERIFICATION].

The RX 7650 GRE deserves a special callout for shoppers and second hand buyers. GRE models have regional history and naming overlap that can confuse owners, especially when translated listings shorten names or when sellers list a card as 7600 series without the suffix [NEEDS VERIFICATION]. If your box or label says 7650 GRE, use only the 7650 GRE package. If it says 7600 XT, use only the 7600 XT package. Suffixes matter here.

The same care applies to Pulse versus Nitro versus Pure subbrands [NEEDS VERIFICATION]. The cited report describes per family updaters, but Sapphire often splits support pages by submodel with distinct part numbers. Start from your exact card page, match the part number on the sticker, match the memory size shown in software, and only then run the updater. A correct family but wrong submodel file is still the wrong file.

Owners who bought prebuilt PCs should also check rather than assume. A prebuilt invoice may say RX 7800 XT without naming Sapphire as the board vendor [NEEDS VERIFICATION]. Open the case or check Device ID and subvendor strings in system tools before flashing a Sapphire package onto what might be another vendor board. When in doubt, ask Sapphire support with photos of labels and a screenshot of the current firmware string.

Finally, keep a record of what you had before the flash. Note the current VBIOS or firmware version string, driver version, motherboard BIOS version, and power supply rating [NEEDS VERIFICATION]. If a later game issue appears, that baseline helps separate a firmware change from a driver change, a Windows update, or a new game patch. A phone photo of the card label plus a text file with version strings takes two minutes and saves hours later.

What Is Not Covered

RX 9000 and RX 6000 are not listed in the cited report, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp. That exclusion is important because it stops owners of newer RDNA 4 cards and older RDNA 2 cards from flashing RX 7000 files in error. If your card is RX 9070, RX 9070 XT, RX 9060 XT, RX 6600, RX 6700 XT, RX 6800, or RX 6950 XT, this specific Sapphire RX 7000 package is not for you [NEEDS VERIFICATION].

The report also does not list mobile RX 7000M parts, workstation cards, or integrated RDNA 3 graphics [NEEDS VERIFICATION]. Laptop owners in particular should never force a desktop board updater onto a mobile GPU. Mobile firmware is tied to the laptop vendor thermal design and power tables, and a desktop flash path can brick a machine or void support. Check your laptop maker support page instead.

Non Sapphire RX 7000 cards are not covered by a Sapphire updater either. Even if the GPU chip matches, board vendors use different power delivery, different cooling control, and different firmware signing [NEEDS VERIFICATION]. An XFX, PowerColor, ASUS, Gigabyte, MSI, ASRock, or reference AMD board needs its own vendor file if and when that vendor releases one. Do not cross flash.

There is also no verified claim in the cited report about Linux specific updaters, DOS boot tools, or UEFI capsule delivery through Windows Update [NEEDS VERIFICATION]. The described format is a per family updater plus install guide plus PDF from Sapphire download listings. Assume Windows based tooling unless Sapphire states otherwise on your exact card page, and read the PDF for OS needs, admin rights, and reboot steps.

Performance, thermals, fan curves, overclock headroom, undervolt stability, and game frame rates are undisclosed in the cited report [NEEDS VERIFICATION]. Do not expect a speed boost from a security firmware. Security fixes sometimes change power sequencing or memory init in ways that alter edge case stability, but there is no verified before and after benchmark tied to this release. Treat any forum benchmark delta as anecdote until a controlled test with version strings is published.

The security content itself is undisclosed. The cited report calls it a joint AMD security finding with no technical details published. There is no verified CVE number, no severity rating, no attack description, no local versus remote distinction, and no statement about active exploitation in that relay [NEEDS VERIFICATION]. That limits risk scoring. The honest posture is to patch promptly because the vendor labels it security, while admitting that outsiders cannot yet quantify urgency.

If you manage multiple PCs, such as a home lab, a small office, or a LAN room, inventory first. List every RX 7000 card by vendor, family, and submodel before downloading anything [NEEDS VERIFICATION]. Flashing eight machines from one USB stick with one family file is exactly how wrong card flashes happen. Keep one folder per card with its updater, its PDF, and a screenshot of the before version.

How To Update Safely

Firmware is not a driver. A driver installs in minutes and rolls back easily, while firmware rewrites low level board code that the card needs to boot [NEEDS VERIFICATION]. A wrong file, a power loss mid flash, or a forced reboot can leave a card unresponsive until recovery steps that many owners cannot perform at home. That is why the tone here is cautious even though the action is prompt.

The cited report points to per family updaters plus guides plus PDFs from Sapphire listings via TechPowerUp, per VideoCardz by WhyCry on October 2, 2026. Those PDFs are the authority for your exact card. The five steps below summarize a safe workflow, but they do not replace the PDF. If the PDF and this article ever disagree, follow the PDF and Sapphire support.

1. Confirm your exact Sapphire model, subbrand, memory size, and part number from the box label, the card sticker, and software detection, and match it to the Sapphire download page for that precise card before you download anything [NEEDS VERIFICATION].
2. Read the PDF guide end to end, noting OS needs, admin rights, antivirus pauses, reboot needs, display cable advice, and any warning not to flash on battery backup, through a hub, or during a storm, plus how to verify the new version after reboot [NEEDS VERIFICATION].
3. Download only the matching family updater from Sapphire for your exact card, verify the file name and version against the support page, keep it on local disk rather than a network share, and close games, overlays, tuning tools, and recording software before launch [NEEDS VERIFICATION].
4. Flash once on stable power with the monitor connected to the target card where the guide requires it, do not touch the mouse or power button during progress, wait for the success prompt, reboot as directed, then verify the new firmware string and check fans, idle temps, and a short game test [NEEDS VERIFICATION].
5. Note what is undisclosed, meaning no public flaw description, no severity score, and no verified performance delta, so record before and after version strings, keep the PDF and installer, and watch Sapphire and AMD channels for a follow up bulletin that explains the joint finding [NEEDS VERIFICATION].

Step one deserves extra emphasis because mismatched flashes cause most user induced bricks [NEEDS VERIFICATION]. RX 7600 versus RX 7600 XT is one character on a listing but a different product. RX 7900 XT versus RX 7900 XTX is one letter but a different board class. RX 7900 GRE versus RX 7900 XT is a different tier with different power needs. Read slowly, match exactly.

Step two matters because Sapphire PDFs often carry model specific cautions that generic how to guides miss [NEEDS VERIFICATION]. Examples can include disabling fast startup, using integrated graphics for display during flash, unplugging secondary cards, or running the tool as administrator. Those details change by family, so forum advice for a 7800 XT may not apply to a 7650 GRE. Your PDF wins.

Step three is about file hygiene. Keep the updater on an internal SSD, note the SHA hash if Sapphire publishes one, and avoid renaming the file [NEEDS VERIFICATION]. If the download page lists multiple revisions, pick the security release that matches the September 16 set described in the report unless Sapphire has posted a newer superseding file with its own notes. When two files both look right, stop and ask support.

Step four is about patience. A firmware progress bar can stall at high percent for a minute while verification runs [NEEDS VERIFICATION]. That pause is normal on some tools and is the worst moment to force a reboot. Wait for an explicit success message, allow the directed reboot, then confirm in software that the version string changed. If the tool reports failure, save the log, photograph the message, and contact support before retrying.

Step five closes the loop. Because technical details are undisclosed, your notes become the audit trail [NEEDS VERIFICATION]. Save before and after screenshots, the PDF name, the updater version, the date, and the driver version. If AMD later assigns a CVE or Sapphire posts a changelog, you will know which machines are already patched and which still need work.

Firmware Versus Driver

Readers often use firmware and driver as synonyms, but they live in different layers [NEEDS VERIFICATION]. Firmware sits on the card and runs at power on, handling init, memory, power rails, and security primitives. The driver sits in Windows and translates game and OS calls into hardware work. Both need updates, but only firmware persists across OS reinstalls and only firmware can brick a card if the wrong image is forced.

That layer split explains why a security fix ships as firmware rather than as Adrenalin software [NEEDS VERIFICATION]. If the issue is in board init, memory training, secure boot chain, or hardware security state, a Windows driver cannot fully fix it. The updater writes corrected low level code to nonvolatile storage, then the driver talks to the fixed hardware. Updating Adrenalin alone would leave the underlying issue in place.

Version checking also differs. Driver versions are easy to see in Adrenalin and in Windows Device Manager [NEEDS VERIFICATION]. Firmware or VBIOS strings often hide in advanced tabs, in GPU Z style tools, or in the updater itself. After this flash, check the same field you recorded before the flash, character for character. A driver number that stayed the same does not mean the firmware failed, because they version independently.

Rollback differs too. Drivers support clean reinstall and rollback through standard installers [NEEDS VERIFICATION]. Firmware often lacks a simple one click rollback, and downgrading may be blocked or unsupported. That asymmetry is why the checklist stresses matching the exact card and reading the PDF first. You can test a driver freely, but you should flash firmware once and correctly.

Risk framing should stay honest without causing panic. The cited report labels this a security update, which favors prompt action, but with no technical details outsiders cannot claim remote exploitability, data theft, or active attacks [NEEDS VERIFICATION]. The balanced message is to prioritize Sapphire RX 7000 owners in the list, patch on stable power with care, and avoid speculative claims about impact until AMD or Sapphire publishes more.

For households with mixed GPUs, update tracking helps. A PC with an RX 7900 XTX for gaming plus an older RX 6600 for a second display only needs the RX 7000 Sapphire file for the supported card, and only if that card is Sapphire [NEEDS VERIFICATION]. Do not flash the unsupported second card. Note each GPU separately, note vendor per GPU, and keep drivers current across both.

Risks and Precautions

The largest risk is a wrong card flash, which can prevent display output on reboot [NEEDS VERIFICATION]. The fix may need integrated graphics, a second card, or a blind recovery process that many owners have never done. Prevention is simple and effective: confirm exact model, use only the matching family updater, and never flash across vendors or across families to save time.

Power stability is the second risk. A blinking room light during a driver install is annoying, but the same blink during firmware verification can corrupt the write [NEEDS VERIFICATION]. Flash on utility power with a healthy supply, avoid storm windows, close heavy loads, and do not flash from a laptop on low battery if the guide involves a laptop with external graphics. If your area has frequent sags, wait for a calm day or use a known good UPS.

Software interference is third. Overlays, tuning utilities, fan control tools, screen recorders, and aggressive antivirus hooks can interfere with low level tools [NEEDS VERIFICATION]. Close Adrenalin tuning, Afterburner style tools, RGB control, and recording apps before launching the updater. Run as administrator where the PDF directs, and allow the reboot without fast startup tricks that skip full init.

The checklist table below turns those cautions into a preflight routine. Work top to bottom, do not skip lines, and abort if any row fails. A delayed patch on a stable card is safer than a rushed patch on a misidentified card.

Backup is often skipped for GPU firmware, yet it still matters [NEEDS VERIFICATION]. Save work, bookmark your PDF, export driver settings if you use custom tuning, and note fan curves. If the updater resets tuning to defaults, you will want those numbers. A screenshot folder dated October 2026 with before and after states is enough.

Warranty and support posture is another gap to handle carefully. The cited report does not quote Sapphire warranty language for interrupted flashes [NEEDS VERIFICATION]. The safe assumption is that user error from a wrong file or forced power off complicates support, while following the PDF exactly gives the cleanest help path. Keep receipts, serial photos, and the updater log if you need to open a ticket.

Second hand buyers face added risk because labels can be missing and coolers can be swapped [NEEDS VERIFICATION]. If the shroud says Nitro but the sticker is gone and software reports a generic RX 7000 string, do not guess. Ask the seller for the original order, check the part number etched on the PCB edge if accessible, or have a shop verify. A mismatched cooler does not change firmware needs, but a misidentified board does.

Mining history, if any, does not change the file choice [NEEDS VERIFICATION]. A card that ran compute loads still needs the same family file as a gaming only card of the same model. What changes is extra caution around thermals and power delivery age. If the card already shows artifacts, crashes, or heat issues, fix hardware health first and ask support whether to flash now or after repair.

Finally, treat forum flash success posts as encouragement, not instructions [NEEDS VERIFICATION]. One owner success with a 7900 XTX does not validate your 7650 GRE file. Board revisions differ, regions differ, and tool versions change. Your Sapphire card page plus your PDF plus the matching updater is the only chain to trust.

FAQ

Which Sapphire cards are covered by this security firmware?
RX 7600, RX 7600 XT, RX 7650 GRE, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XT, and RX 7900 XTX are covered, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp.

When was the firmware available and when was it spotted?
The files were available since September 16 and spotted on October 2, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp.

Is this a driver update or a firmware update?
It is firmware, not a driver, so it rewrites low level board code and needs exact matching and stable power, with rollback often limited [NEEDS VERIFICATION].

Are RX 9000 or RX 6000 cards included?
No, RX 9000 and RX 6000 are not listed in the cited report, so owners of those generations should not use RX 7000 files and should wait for their own vendor guidance [NEEDS VERIFICATION].

What security issue does it fix?
The cited report describes a joint AMD security finding with no technical details published, so there is no verified CVE, severity score, or attack description to quote yet [NEEDS VERIFICATION].

What should I do before flashing?
Confirm the exact Sapphire model, read the PDF guide, download only the matching family updater, and verify the new version after reboot on stable power [NEEDS VERIFICATION].

Bottom Line

Sapphire owners of the 8 listed RX 7000 cards should treat this as a prompt security update, not an optional tune up. The verified facts are narrow but clear: 8 families from RX 7600 through RX 7900 XTX, per family updater plus guide plus PDF, available since September 16 and spotted October 2, framed as a joint AMD security finding with no technical details, per VideoCardz by WhyCry on October 2, 2026 relaying Sapphire via TechPowerUp.

The safe path is exact matching and careful power. Confirm model, read PDF, download matching updater, flash and verify, and note what remains undisclosed. Skip the flash if your card is RX 9000, RX 6000, mobile, or another vendor, and wait for that vendor own file [NEEDS VERIFICATION]. Keep before and after version notes so a later bulletin can be mapped to your PCs without guesswork.

Sources: VideoCardz report by WhyCry on October 2, 2026 at VideoCardz relaying Sapphire download listings surfaced via TechPowerUp, with card support files from Sapphire. Technical flaw details, severity, performance impact, and version strings beyond that relay are marked [NEEDS VERIFICATION] pending a Sapphire or AMD bulletin.