CVE-2025-41690 — Endress+Hauser: Proline 10 Maintenance credentials may be exposed under certain conditions

A low-privileged attacker in bluetooth range may be able to access the password of a higher-privilege user (Maintenance) by viewing the device’s event log. This vulnerability could allow the Operator to authenticate as the Maintenance user, thereby gaining unauthorized access to sensitive configuration settings and the ability to modify device parameters.

Published Sep 2, 2025Updated Sep 2, 2025Sources: cvelistV5, CERTVDE

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

endress hauser

6 products listed

CVSS base

7.4

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

endress hauser

Products (6)

promag 10 with hartpromag 10 with io linkpromag 10 with modbuspromass 10 with hartpromass 10 with io linkpromass 10 with modbus

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.4	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-532

References

1 on the record

certvde.com/en/advisories/VDE-2025-068
reference

Elsewhere on this site

endress hauserevery CVE for this vendor
CWE-532other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.