Skip to main content
VulnerabilityPublished

CVE-2026-67529: opf openproject · Information Exposure

Affects opf openprojectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 17.6.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 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 29 Oct 2026.

What to do

Upgrade openproject and opf/openproject to 17.6.0.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • <17.6.0
Fixed in
  • 17.6.0
GitHubopf/openprojectpkg:github/opf/openprojectOther threatsAffected
  • <17.6.0
Fixed in
  • 17.6.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.6.0 or later, where this vulnerability is fixed. Users should verify that their OpenProject instances are updated to prevent unauthorized exposure of private work package information.

Description

OpenProject versions prior to 17.6.0 have a vulnerability where certain API endpoints expose private work package titles and IDs to users who have permission to view time or cost entries but not the work packages themselves. This occurs because the API renders work package links without verifying if the user has visibility permissions. The issue is fixed in version 17.6.0.

References

Community reviews

Loading reviews…