Friday, October 2nd 2026

Sapphire Radeon RX 7000 Series Cards Get vBIOS Security Update

AMD Radeon RX 7000 series RDNA 3 graphics cards today received a new vBIOS security update. According to AMD's add-in card partner Sapphire, the update is now available for Sapphire's own Radeon RX 7600, RX 7600 XT, RX 7650 GRE, RX 7700 XT, RX 7800 XT, RX 7900 GRE, RX 7900 XT, and RX 7900 XTX models. This update covers all the desktop graphics cards that AMD released for the RDNA 3 lineup and marks one of the rare occurrences of GPU vBIOS updates in recent times. Typically, these vBIOS updates are reserved for security patches, and Sapphire confirms that the company has been working to address a security issue identified in partnership with AMD.

Before updating the GPU firmware, ensure that the AMD Adrenalin Edition graphics driver is installed and that you have about 15-20 minutes to complete the update. To update the GPU firmware, Sapphire provides links to the specific GPU model affected. Once downloaded, run the updater as an administrator, choose a folder to save the executable files, and locate that folder. Once inside, run the program as an administrator again, and the AMD Radeon Firmware Updater tool will start. This tool will detect any AMD GPU present and indicate if there is a new firmware update. As shown in the example below, select the GPU and run the update, which will prompt a reboot once it is finished. Note that for the Radeon RX/PRO 7000 Series, the tool automatically runs twice: once in regular mode and a second time in safe mode to complete the process.
After installation, confirm that the new GPU vBIOS firmware update is completed using the AMD Adrenalin software, which will display the exact firmware version installed on your graphics card. For reference on the installation process, follow Sapphire's installation guide step-by-step, though it should be fairly straightforward.
Source: Sapphire
Add your own comment

32 Comments on Sapphire Radeon RX 7000 Series Cards Get vBIOS Security Update

#1
Spacemarkl
Never updated a GPU Bios since Voodoo times. Fingers crossed, I won't brick mine.
Posted on Reply
#2
lambda
Interesting that only Sapphire cards require an update. I'm not seeing anything from other vendors, maybe it's too early to make a comment.
Posted on Reply
#3
AleksandarK
News Editor
SpacemarklNever updated a GPU Bios since Voodoo times. Fingers crossed, I won't brick mine.
I think I have never updated the GPU BIOS in my life! BTW, just follow the instructions; there's no way to brick it, it's just regular firmware updating.
Posted on Reply
#4
Chrispy_
I've never heard of a security update for a GPU. The only times I've had to do official firmware updates in the past were for errata in the launch firmware, always problems with detection or displayport on Nvidia generations going back to the 600-series IIRC.

Security update? Surely if your Radeon is in a compromised machine, your whole machine is compromised. Radeons don't run an OS, do they?
Posted on Reply
#5
FR3D1
Ninja Cat
AleksandarKI think I have never updated the GPU BIOS in my life!
I've even had experience with "blind" flashing. It's less complicated than you might initially think.

Regards,
Fred.
Posted on Reply
#6
_JP_
AMD hasn't published a specific CVE on their site for this, unless I'm missing which one it is. :confused:
Posted on Reply
#7
_roman_
I would not do that. AMD has disabled certain overclocking and sensor functions on my radeon 7800xt with the loadable linux-firmware package. when you flash it, the extra fps may be gone for sure now.

@FR3D1 These are not my findings, i just verified it myself and wrote it a bit cryptic
_roman_ in AMD removed sensor output and partly access to the Powercolor 7800XT hellhound graphic card / gnu userspace & linux kernel. // Radeon 9070XTIn short AMD removed sensor readout functionality from my powercolor 7800xt hellhound graphic card. I found this by chance. I dig into. Learnt a few informations. this firmware is defective: sys-kerne…
Fact is, this is the last firmware file which worked before i put the 7800xt in the cartoon box in may 2026,
-rw-r--r-- 1 root root 266K Apr 3 03:36 smu_13_0_10.bin

-- Anyway, when you are in the overclocking business or when you want higher resale value in the next few months for your graphic card, I would personally not flash the firmware. My graphic card is still not sold but will go to the 2nd hand market. Some forum indicate my current in use radeon 9070 has similar feature for much more fps, windows is already locked what i read.

My msi motherboard exposes now more clearly the hybrid graphics. I would also check when it is critical to use the motherboard cpu graphics, e.g. ryzen 7700x which works fine, and use via driver teh radeon 9070 OC graphics as support. basically run your secure os when you are not gaming on the cpu graphics and use the "security" not updated firmware gpu in your gaming installation.

You have been warned about my concern.

I assume software writes directly via hidden bus to certain hardware registers to set certain values which stay persistent and give you more heat on the graphic card and more fps. I do know about ucontroller, i was only reading a bit 01 / 2026 about it. the firmware blocks access to the hidden bus, which is when i am not wrong, a renamed i2c bus.
Posted on Reply
#8
dgianstefani
TPU Proofreader
AleksandarKI think I have never updated the GPU BIOS in my life! BTW, just follow the instructions; there's no way to brick it, it's just regular firmware updating.
It won't necessarily be permanently "bricked", but in any situation where it fails, and it can fail, you get no display output, so now you have to use iGPU (if you have it) or connect another DGPU (while the original GPU is still attached so you can program it again) for display output, and proceed to try again, unless you can figure out a way for your PC to turn on with no display output, and enter all the commands in all the software without being able to see it. What if you don't have an iGPU, what if you don't have a spare dGPU, what if your motherboard is ITX/mATX and only has one x16 slot? Lots of potential issues.

It's one of the reasons why they are so hesitant to push GPU firmware updates, and try to fix everything in software drivers. 99% of the time that's enough, but for example here, it isn't.
Posted on Reply
#9
Falck
Ok, so 'security'? Care to elaborate on what that actually entails so I can make an informed decision about whether to update or skip it? When would I actually need it, and are there any drawbacks?
Posted on Reply
#10
Balrogos
SpacemarklNever updated a GPU Bios since Voodoo times. Fingers crossed, I won't brick mine.
:o i updates bios for HD 7970 and GTX 1070 :) and RX 570
Posted on Reply
#11
Makaveli
Nice I have not had to touch a bios update on a GPU in a very long time.

Lets hope XFX does the same for their models.
Posted on Reply
#12
Jism
_roman_I would not do that. AMD has disabled certain overclocking and sensor functions on my radeon 7800xt with the loadable linux-firmware package. when you flash it, the extra fps may be gone for sure now.

You have been warned about my concern.
Mostly it's about warranty protection. How many people do overvolt values that have no business to be fair and end up with bricked card, sending it back for RMA?

I still run a 6700XT and i'm "glad" it's one of the few generations that still works with MPT. You can easily increase the default 180W into a 300W card with clocks up to 2.8 ~ 2.9Ghz for quite the improvement.
Posted on Reply
#14
mechtech
honestly with the cost of GPUs, the FW should be actively developed and released for those who want/need it, whether for compatibility, improved power consumption, etc. etc.
Posted on Reply
#15
Spacemarkl
Ok, I dared the update and everything went smooth. GPU is working great and I am calm (and feel more secure I guess).
Posted on Reply
#16
warrior420
If AMD/Sapphire haven't posted the vulnerability info, that means it's bad. I mean, we are talking about an actual firmware/hardware-level vunerability here. It's good they aren't blabbering about it and screwing a bunch of 7000 series owners.

I just wonder if my 6900XT is effected, or if this card is even on their radar. 😣
Posted on Reply
#17
_JP_
No, that is FUD. Especially because of that that the process for a vulnerability disclosure is to provide the patch and publish the CVE. It happens all of the time.
That way, you would also have a clarification of it affects your card or not. It would put you in a position to ask the AIB for an update or an answer as to why not.
Posted on Reply
#18
Contra
How this fix worked on dual Vbios cards?
Posted on Reply
#19
Spacemarkl
ContraHow this fix worked on dual Vbios cards?
Probably it will flash the currently active BIOS, so that you have to switch if you want to flas both.
Posted on Reply
#20
Aerpoweron
SpacemarklNever updated a GPU Bios since Voodoo times. Fingers crossed, I won't brick mine.
I updated my Nvidia GTX 660ti to get a UEFI compatible bios on it.
But yep, GPU bios updates are rare.
Posted on Reply
#21
pascalampertail
Worth noting this update DOESN'T seem to apply to Sapphire cards that are based on the AMD Reference design. I have a reference design Sapphire 7800XT As seen here and the bios updater doesn't even pick up that it exists. Didn't see anything on Sapphire's website claiming these cards would be excluded but I guess they are for whatever reason.
Posted on Reply
#22
cmdr_scotty
Interesting that they're publishing new vbios for the sapphire cards.

But considering I cross flashed my 7900xtx pulse to the nitro+ vbios. I'm less inclined to consider this update.

It was already a pain to get it to accept the bios and ignore the hardware ID mismatch, don't want it to flash it back to the pulse bios.
Posted on Reply
#23
Jo3yization
FalckOk, so 'security'? Care to elaborate on what that actually entails so I can make an informed decision about whether to update or skip it? When would I actually need it, and are there any drawbacks?
Exactly like wth. We've all heard of planned obscelence & an obscure security issue affecting only one AIB makes very little sense.
Posted on Reply
#24
Plexiglas
The UEFI GOP for Sapphire RDNA3 expired in 2023 which prevented Bitlocker binding in 7, 11 PCR config to the TPM. The workaround was deleting the GOP signing key for secureboot - this meant you couldn't use the GPU in the UEFI but at least Bitlocker would now bind properly.

Haven't updated it yet, but hoping this "fix" is for this problem.

Will update if it is In fact a fix for the GOP signing keys.
Posted on Reply
#25
Rulumi
PlexiglasHaven't updated it yet, but hoping this "fix" is for this problem.
The update is to fix a yet undisclosed to the public CVE, but they could have also updated that if they wanted.

Someone with a Sapphire RDNA 3 GPU that applied the update should be able to check if that was also updated or not.
Posted on Reply
Add your own comment
Nov 11th, 2026 23:56 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts