VulnerabilityPublished 9 Jan 2026

CVE-2025-67278: tim-bpm-suite · Incorrect Privilege Assignment

Affects tim-bpm-suiteSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.1.2 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.1.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade com.timsolution/tim-bpm-suite and com.timsolution/tim-flow to 9.1.2.

Affected software

Product	Affected	Fixed in
Mavencom.timsolution/tim-bpm-suite`pkg:maven/com.timsolution/tim-bpm-suite`Other threats	Affected <9.1.2	Fixed in 9.1.2
Mavencom.timsolution/tim-flow`pkg:maven/com.timsolution/tim-flow`Other threats	Affected <9.1.2	Fixed in 9.1.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, network-level mitigations should be implemented, including restricting access to TIM BPM Suite and TIM FLOW management interfaces to trusted IP addresses via firewalls or VPNs. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious HTTP requests that could exploit this vulnerability. Conduct thorough logging and monitoring of HTTP traffic to identify anomalous patterns indicative of exploitation attempts. Review and tighten access controls and user privileges within the affected systems to minimize the impact of any potential escalation. Additionally, perform regular security assessments and penetration tests focusing on BPM and workflow platforms to detect similar vulnerabilities. Educate IT and security teams about this vulnerability to ensure rapid response capability. Finally, consider network segmentation to isolate BPM platforms from critical infrastructure to limit lateral movement in case of compromise.

Description

An issue in TIM Solution GmbH TIM BPM Suite & TIM FLOW before v.9.1.2 allows a remote attacker to escalate privileges via a crafted HTTP request

Impact

For European organizations, the impact of CVE-2025-67278 could be substantial, particularly for those in industries such as manufacturing, finance, healthcare, and government that rely on TIM BPM Suite and TIM FLOW for process automation and workflow management. Successful exploitation could lead to unauthorized privilege escalation, enabling attackers to manipulate or disrupt business processes, access sensitive data, or deploy further attacks within the network. This could result in operational downtime, data breaches, regulatory non-compliance, and reputational damage. Given the remote exploitation vector and lack of authentication requirement, attackers could launch attacks from outside the organization’s perimeter, increasing the risk of widespread compromise. The absence of known exploits in the wild currently limits immediate impact, but the vulnerability's publication may prompt threat actors to develop exploits. European organizations with complex workflows and integrations dependent on these platforms are particularly vulnerable to cascading effects from such privilege escalations.

CWE-266Incorrect Privilege Assignment (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 16:10 UTC

WeaknessesCWE-266

Technical details

References

Community reviews

Related threats