dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-44352

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flowsint is an open-source OSINT graph exploration tool designed for cybersecurity investigation, transparency, and verification. Prior to 1.2.3, Broken Access Control allows reading of sketch logs from any user. This vulnerability is fixed in 1.2.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Broken Access Control in Flowsint OSINT tool versions prior to 1.2.3 allows authenticated users to read sketch logs from other users due to missing or insufficient authorization checks on log access endpoints, enabling unauthorized cross-user data disclosure.

MitigationUpgrade to Flowsint version 1.2.3 or later. If immediate upgrade is not feasible, implement proper authorization validation on log retrieval endpoints to enforce user-specific access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Flowsint installation and version
    Locate the Flowsint application directory and check for a version file, changelog, or query the application using --version or /api/version endpoint if available. Also check startup logs for version information.
    Affected if Version is prior to 1.2.3 (any 1.x.x version below 1.2.3) or version cannot be determined
  2. Verify user authentication is enabled
    Check Flowsint configuration files (typically in config/ or settings/) for authentication settings. Look for session management, user login configuration, or authentication middleware settings.
    Affected if Authentication is enabled and users can log in (required condition for this vulnerability)
  3. Confirm log access functionality exists
    Identify if Flowsint has sketch log viewing capability. Check for log-related API endpoints, UI components for log access, or log storage directories. Look for endpoints containing /logs/, /sketch/, or similar paths.
    Affected if Log access feature is present and accessible to authenticated users
  4. Check for user-specific authorization on log endpoints
    Review application access control configuration, endpoint permission settings, or code that handles log retrieval. Test whether an authenticated user can access logs belonging to a different user by manipulating user IDs or session tokens in log access requests.
    Affected if No user-specific authorization enforcement found on log retrieval endpoints, allowing cross-user log access

A user is affected if Flowsint version is prior to 1.2.3 AND authentication is enabled AND the log access feature is accessible without proper per-user authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Flowsint version 1.2.3 or later. If immediate upgrade is not feasible, implement proper authorization validation on log retrieval endpoints to enforce user-specific access controls.

Recommended fix High confidence

1.2.3

  1. 1. Identify the currently installed Flowsint version using the project's version check command or package manager
  2. 2. Navigate to the official Flowsint GitHub repository (github.com)
  3. 3. Download or clone version 1.2.3 of Flowsint
  4. 4. Replace the existing installation with the new version 1.2.3
  5. 5. Verify the upgrade was successful by checking the version number
  6. 6. Test that the access control fix is working by attempting to access sketch logs (should now be restricted to authorized users only)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44352 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data