CVE-2022-36173: FreshService macOS Agent < 4.4.0 and FreshServce Linux Agent < 3.4.0 are vulnerable to TLS Man-in-The-Middle v

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

freshservice agent: upgrade to 2.12.0; freshservice agent: upgrade to 3.4.0; freshservice agent: upgrade to 4.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-36173 being exploited?

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

CVE-2022-36173 affects freshservice agent, freshservice agent, freshservice agent. Severity is high (CVSS 8.1). FreshService macOS Agent < 4.4.0 and FreshServce Linux Agent < 3.4.0 are vulnerable to TLS Man-in-The-Middle via the FreshAgent client and scheduled update service.

Q: How urgent is CVE-2022-36173?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

HIGH 8.1REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2022-36173 is a high-severity flaw (CVSS 8.1) affecting freshservice agent, freshservice agent, freshservice agent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

FreshService macOS Agent < 4.4.0 and FreshServce Linux Agent < 3.4.0 are vulnerable to TLS Man-in-The-Middle via the FreshAgent client and scheduled update service.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-295
Published	2022-09-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: freshworks

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

Am I affected?

Timeline

2022-09-12 21:15 UTCPublished CVE record published
2026-06-17 04:53 UTCUpdated Record last modified

freshworks freshservice agent UPGRADE

Affected: < 2.12.0

Fixed in: 2.12.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy freshservice-agent || rpm -q freshservice-agent || freshservice-agent --version

2. UPGRADE to 2.12.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade freshservice-agent

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade freshservice-agent

Note

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

freshworks freshservice agent UPGRADE

Affected: < 3.4.0

Fixed in: 3.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy freshservice-agent || rpm -q freshservice-agent || freshservice-agent --version

2. UPGRADE to 3.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade freshservice-agent

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade freshservice-agent

Note

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

freshworks freshservice agent UPGRADE

Affected: < 4.4.0

Fixed in: 4.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy freshservice-agent || rpm -q freshservice-agent || freshservice-agent --version

2. UPGRADE to 4.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade freshservice-agent

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade freshservice-agent

Note

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

freshworks freshservice probe UPGRADE

Affected: < 4.11.0

Fixed in: 4.11.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy freshservice-probe || rpm -q freshservice-probe || freshservice-probe --version

2. UPGRADE to 4.11.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade freshservice-probe

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade freshservice-probe

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-36173?

freshservice agent: upgrade to 2.12.0; freshservice agent: upgrade to 3.4.0; freshservice agent: upgrade to 4.4.0. Exact commands for each OS are on this page.

Is CVE-2022-36173 being exploited?

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

CVE-2022-36173 affects freshservice agent, freshservice agent, freshservice agent. Severity is high (CVSS 8.1). FreshService macOS Agent < 4.4.0 and FreshServce Linux Agent < 3.4.0 are vulnerable to TLS Man-in-The-Middle via the FreshAgent client and scheduled update service.

How urgent is CVE-2022-36173?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

macOS vulnerabilities

Related CVEs

CVE-2022-36174 HIGH 8.1 UPGRADE UPGRADE FreshService Windows Agent < 2.11.0 and FreshService macOS Agent < 4.2.0 and FreshService Linux Agent < 3.3.0

References

← Back to latest CVEs