An issue was discovered in BAE SOCET GXP before 4.6.0.2.

published 2025-10-27 last yr. modified 2026-11-05 4d ago also EUVD-2025-36207

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits: 0; none known

An issue was discovered in BAE SOCET GXP before 4.6.0.2. The SOCET GXP Job Status Service fails to authenticate requests. In some configurations, this may allow remote or local users to abort jobs or read information without the permissions of the job owner.

Patch / fix

fixed in 1

baesystems socet_gxp 4.6.0.2

Is CVE-2025-54970 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

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: last yr. (2025-10-28)

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Classification

Weakness

CWE-284 Improper Access Control

References

geospatialexploitationproducts.com /content/socet-gxp/vulnerabilities-disclosure/#cve-2025-54970
mitigation, vendor-advisory
baesystems.com /en-us/product/geospatial-exploitation-products
product

Sources

CVE List CVE-2025-54970
NVD CVE-2025-54970

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.