logseq / logseq/logseq

5 unpachted security vulnerabilities with CVE?

Open
#12,838 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

https://github.com/advisories?query=logseq

Image

### Reproduce the Bug

.

### Expected Behavior

_No response_

### Screenshots

_No response_

### Desktop or Mobile Platform Information

_No response_

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the GitHub Advisories search for logseq linked in the issue and review the attached screenshot to identify the five reported vulnerabilities. Confirm which findings apply to this repository and define completion as having each vulnerability assessed and an agreed remediation or tracking outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.