Safe Software FME Server v2021.2.5 and below does not employ server-side validation.

published 2022-09-19 4y ago modified 2026-06-17 4mo ago also EUVD-2022-40931

cvss: 7.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits: 0; none known

Patch / fix

fixed in 1 links 1

safe fme_server 2021.2.6

community.safe.com/s/article/Known-Issue-Lack-of-server-side-validation-when-… advisory

Is CVE-2022-38341 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

References

community.safe.com /s/article/Known-Issue-Lack-of-server-side-validation-when-creating-a-new-user-in-FME-Server
patch, vendor-advisory
cycura.com /blog/safe-software-inc-fme-server-vulnerability-disclosure/
third-party-advisory

Sources

CVE List CVE-2022-38341
NVD CVE-2022-38341

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.