Skip to main content
VulnerabilityPublished

CVE-2026-44736: opf openproject · Information Exposure

Affects opf openprojectSource CVE Database V5

0
Compare

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

Data as of 8 Nov 2026, 23:24 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 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.4.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 8 Nov 2026.

What to do

Upgrade openproject and opf/openproject to 17.4.0.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • <17.4.0
Fixed in
  • 17.4.0
GitHubopf/openprojectpkg:github/opf/openprojectOther threatsAffected
  • <17.4.0
Fixed in
  • 17.4.0

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

AI-suggested

Upgrade OpenProject to version 17.4.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

OpenProject is open-source, web-based project management software. Prior to 17.4.0, the GET /api/v3/relations endpoint allows any authenticated user to retrieve relations — and the subject (title) of work packages they have no permission to view — by supplying an arbitrary work package ID in the involved, fromId, or toId filter. This bypasses the Relation.visible scope due to a flawed performance optimization in RelationQuery. This vulnerability is fixed in 17.4.0.

References

Community reviews

Loading reviews…