CVE-2022-28747: Key reuse in GoSecure Titan Inbox Detection & Response (IDR) through 2022-04-05 leads to remote code execution

Q: How do I fix CVE-2022-28747?

titan inbox detection \& response: upgrade to 4.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-28747 being exploited?

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

Q: What does CVE-2022-28747 affect?

CVE-2022-28747 affects titan inbox detection \& response. Severity is critical (CVSS 9.8). Key reuse in GoSecure Titan Inbox Detection & Response (IDR) through 2022-04-05 leads to remote code execution. To exploit this vulnerability, an attacker must craft and sign a serialized payload.

Q: How urgent is CVE-2022-28747?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-28747 is a critical-severity flaw (CVSS 9.8) affecting titan inbox detection \& response. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Key reuse in GoSecure Titan Inbox Detection & Response (IDR) through 2022-04-05 leads to remote code execution. To exploit this vulnerability, an attacker must craft and sign a serialized payload.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Published	2022-08-25
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: gosecure

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

Am I affected?

Timeline

2022-08-25 23:15 UTCPublished CVE record published
2026-06-17 04:38 UTCUpdated Record last modified

gosecure titan inbox detection \& response UPGRADE

Affected: < 4.1.1

Fixed in: 4.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy titan-inbox-detection--response || rpm -q titan-inbox-detection--response || titan-inbox-detection--response --version

2. UPGRADE to 4.1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade titan-inbox-detection--response

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade titan-inbox-detection--response

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2022-28747?

titan inbox detection \& response: upgrade to 4.1.1. Exact commands for each OS are on this page.

Is CVE-2022-28747 being exploited?

CVE-2022-28747 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-2022-28747 affect?

CVE-2022-28747 affects titan inbox detection \& response. Severity is critical (CVSS 9.8). Key reuse in GoSecure Titan Inbox Detection & Response (IDR) through 2022-04-05 leads to remote code execution. To exploit this vulnerability, an attacker must craft and sign a serialized payload.

How urgent is CVE-2022-28747?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs