Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-1346: IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through

36
This month
CRITICAL 9.3UPGRADEUPGRADEUPGRADE

CVE-2026-1346 is a critical-severity flaw (CVSS 9.3) affecting security verify access, security verify access container, verify identity access. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow a locally authenticated user to escalate their privileges to root due to execution with unnecessary privileges than required.

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.3 (Critical)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 87%)
CISA exploited listNo
WeaknessCWE-250
Published2026-04-08
Last modified2026-07-25
Publisher (CNA): IBM Corporation · Vendor: ibm

Share: LinkedIn · X · Reddit

Last updated 2026-07-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

ibm security verify access UPGRADE
Affected: >= 10.0.0 and <= 10.0.9.1
Fixed in: newer than 10.0.9.1
Safe to downgrade to: a release before 10.0.0
1. Check installed version
apt-cache policy security-verify-access || rpm -q security-verify-access || security-verify-access --version
2. UPGRADE to newer than 10.0.9.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-verify-access
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-verify-access
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 10.0.0 (Debian / Ubuntu)
apt-cache madison security-verify-access sudo apt install security-verify-access=<VERSION_BEFORE_10.0.0> sudo apt-mark hold security-verify-access
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-verify-access sudo dnf downgrade security-verify-access-<VERSION_BEFORE_10.0.0> sudo dnf versionlock add security-verify-access
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ibm security verify access container UPGRADE
Affected: >= 10.0.0.0 and <= 10.0.9.1
Fixed in: newer than 10.0.9.1
Safe to downgrade to: a release before 10.0.0.0
1. Check installed version
apt-cache policy security-verify-access-container || rpm -q security-verify-access-container || security-verify-access-container --version
2. UPGRADE to newer than 10.0.9.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade security-verify-access-container
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade security-verify-access-container
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 10.0.0.0 (Debian / Ubuntu)
apt-cache madison security-verify-access-container sudo apt install security-verify-access-container=<VERSION_BEFORE_10.0.0.0> sudo apt-mark hold security-verify-access-container
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list security-verify-access-container sudo dnf downgrade security-verify-access-container-<VERSION_BEFORE_10.0.0.0> sudo dnf versionlock add security-verify-access-container
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ibm verify identity access UPGRADE
Affected: >= 11.0.0.0 and <= 11.0.2.0
Fixed in: newer than 11.0.2.0
Safe to downgrade to: a release before 11.0.0.0
1. Check installed version
apt-cache policy verify-identity-access || rpm -q verify-identity-access || verify-identity-access --version
2. UPGRADE to newer than 11.0.2.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade verify-identity-access
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade verify-identity-access
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 11.0.0.0 (Debian / Ubuntu)
apt-cache madison verify-identity-access sudo apt install verify-identity-access=<VERSION_BEFORE_11.0.0.0> sudo apt-mark hold verify-identity-access
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list verify-identity-access sudo dnf downgrade verify-identity-access-<VERSION_BEFORE_11.0.0.0> sudo dnf versionlock add verify-identity-access
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ibm verify identity access container UPGRADE
Affected: >= 11.0.0.0 and <= 11.0.2.0
Fixed in: newer than 11.0.2.0
Safe to downgrade to: a release before 11.0.0.0
1. Check installed version
apt-cache policy verify-identity-access-container || rpm -q verify-identity-access-container || verify-identity-access-container --version
2. UPGRADE to newer than 11.0.2.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade verify-identity-access-container
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade verify-identity-access-container
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 11.0.0.0 (Debian / Ubuntu)
apt-cache madison verify-identity-access-container sudo apt install verify-identity-access-container=<VERSION_BEFORE_11.0.0.0> sudo apt-mark hold verify-identity-access-container
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list verify-identity-access-container sudo dnf downgrade verify-identity-access-container-<VERSION_BEFORE_11.0.0.0> sudo dnf versionlock add verify-identity-access-container
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-1346?

security verify access: upgrade to newer than 10.0.9.1; security verify access container: upgrade to newer than 10.0.9.1; verify identity access: upgrade to newer than 11.0.2.0. Exact commands for each OS are on this page.

Is CVE-2026-1346 being exploited?

CVE-2026-1346 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-1346 affect?

CVE-2026-1346 affects security verify access, security verify access container, verify identity access. Severity is critical (CVSS 9.3). IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow a lo

How urgent is CVE-2026-1346?

Priority 36/100. Critical severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.