Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Low · CVSS 2.3

How to Fix CVE-2026-33447: Secure Access (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-33447 is a sibling vulnerability in the same vendor advisory as CVE-2026-33446. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 2.3 - Low
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-33446
Fixed inSame patched build as CVE-2026-33446 (See vendor advisory)
Type (CWE)Not verified

What's different about CVE-2026-33447?

CVE-2026-33447 is a buffer overflow in a message parsing function of the

Secure Access client prior to 14.50. Attackers with control of a

modified server can send a special packet that can overwrite a small

portion of memory conceivably leading to memory corruption or denial of

service.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-33447

Apply the patched build per the primary write-up: How to Fix CVE-2026-33446.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-33447 fixed by the same patch as CVE-2026-33446?

Yes. CVE-2026-33447 ships in the same vendor advisory as CVE-2026-33446. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-33447?

The CVSS base score is 2.3 (Low).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the Secure Access bundle. Full procedure at CVE-2026-33446.*