Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 02:05 UTC

Critical in the last 24 hours

1603 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

144-76% vs 7-day avg of 597

2 critical, 38 high, 59 medium, 25 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Critical	9.9	CVE-2026-115933	Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for GitroomHQGitroomHQ postiz-app	NVD	Oct 24 15:17 UTC
CVE-2026-115933Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for Executive summary A flaw in the Postiz social media scheduling app (GitroomHQ postiz-app, versions 2.15.0 and later) lets any registered user forge trusted tokens and take over other users' accounts and organizations. The advisory rates it Critical with a CVSS v3.1 score of 9.9. The vendor's fix is to update to version 2.25.3, and until then the advisory recommends blocking the extension-refresh route and disabling self-registration, which reduce but do not remove the risk. Technical summary The root cause is that Postiz signs session, invitation and password reset tokens with one shared secret and no marker of their purpose, and a browser-extension credential refresh route signs request-controlled data and stores it where the user can read it back (CWE-290, CWE-345, CWE-915). An attacker needs only an ordinary self-registered account, with network access and no user interaction. Affected versions are stated as 2.15.0 and later, and the fix is in 2.25.3 (commit a5affe62). The advisory gives workarounds: block POST /integrations/extension-refresh at the reverse proxy, which does not close the team invitation route, and set DISABLE_REGISTRATION=true. Specific detection guidance is not stated. Whether the instance must reach api2.skool.com is stated as a configuration condition, and no exploitation in the wild is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from gadvisory.org/advisories/PSA-2026-YT2HMH Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Changed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Affects GitroomHQ GitroomHQ postiz-app NIST National Vulnerability DatabasePublished Oct 24, 2026 15:17 UTC Read the advisory
	Critical	9.6	CVE-2026-115932	When a post is published, Postiz treats a media path that is not a web address as a file on the server's disk, but it does not check that the file lies inside the upload directory GitroomHQ, PostizGitroomHQ postiz-app, Postiz	NVD	Oct 24 13:16 UTC
CVE-2026-115932When a post is published, Postiz treats a media path that is not a web address as a file on the server's disk, but it does not check that the file lies inside the upload directory Executive summary A path traversal flaw in Postiz (GitroomHQ postiz-app) lets any registered user read arbitrary files on the server and have them sent to a Discord server the user controls, when the Discord provider is enabled. The advisory rates it Critical with a CVSS v3.1 score of 9.6, and the vendor's fix is to upgrade to version 2.25.3 or later. Until then, the advisory recommends setting DISABLE_REGISTRATION to true, which reduces exposure but does not close the issue. Technical summary The flaw is classified as CWE-22 (path traversal) and CWE-74 (injection). When a post is published, a media path that is not a web address is treated as a local file without checking that it lies inside the upload directory, so an authenticated user with an ordinary account can have the publishing worker read arbitrary files and deliver them as attachments. The affected range is given as 2.23.0 or later (≥ 2.23.0), and the fixed version is 2.25.3. The main route requires DISCORD_CLIENT_ID, DISCORD_CLIENT_SECRET and DISCORD_BOT_TOKEN_ID to be set, and the validation-time route requires a Dribbble, TikTok or Pinterest provider; the advisory states that the worker runs as root in the shipped container. Mitigations are to set DISABLE_REGISTRATION=true and leave the Discord provider credentials unset, though the advisory says these only reduce reach. The advisory does not state any detection guidance, and the publicly referenced fix is commit 12db9bd. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from gadvisory.org/advisories/PSA-2026-E9AHFV Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Changed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N Affects GitroomHQ Postiz GitroomHQ postiz-app Postiz NIST National Vulnerability DatabasePublished Oct 24, 2026 13:16 UTC Read the advisory
	Critical	9.9	CVE-2026-115931	Postiz lets a signed-in user ask the backend to run a function on one of their connected channels GitroomHQGitroomHQ postiz-app	NVD	Oct 23 23:17 UTC
CVE-2026-115931Postiz lets a signed-in user ask the backend to run a function on one of their connected channels Executive summary A flaw in the Postiz social media scheduling application, published by GitroomHQ, lets any signed-in user read files and environment secrets from the server and crash the backend. The advisory rates it Critical with a CVSS v3.1 score of 9.9, and says registration must be closed to reduce exposure, but this does not fix the issue. The vendor's recommended fix is to upgrade to version 2.25.2. Technical summary The backend does not restrict which internal helper functions a signed-in user can invoke through the channel-function interface, classified as CWE-470 and CWE-73. A user who connects a channel whose stored token is a file path can make the backend return any file it can read, including its environment, which exposes the JWT signing secret, database and Redis connection strings, and provider credentials. A separate request terminates the backend process and can be repeated after each restart. The advisory states affected versions as 2.23.0 and later, with the fix in 2.25.2, and references commit 9383f5b as the patch. Self-registration is open by default, and setting DISABLE_REGISTRATION=true is given as a partial mitigation only. Detection guidance and exploitation in the wild are not stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from gadvisory.org/advisories/PSA-2026-JNXM56 Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Changed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Affects GitroomHQ GitroomHQ postiz-app NIST National Vulnerability DatabasePublished Oct 23, 2026 23:17 UTC Read the advisory
	Medium	5.3	CVE-2026-107761	Several Postiz endpoints return the complete database row of the record they operate on instead of only the fields the client needs GitroomHQGitroomHQ postiz-app	NVD	Oct 11 16:16 UTC
CVE-2026-107761Several Postiz endpoints return the complete database row of the record they operate on instead of only the fields the client needs From the advisory Several Postiz endpoints return the complete database row of the record they operate on instead of only the fields the client needs. Two of them include secrets the caller is not meant to receive. The public API's channel delete returns the deleted integration row, including the channel's platform access token and refresh token. A third-party OAuth app permitted to delete a channel therefore receives that channel's social platform credentials and can use them against the connected account directly, outside Postiz. `GET /user/organizations` returns each organization row, including its API key, to every member of the organization. The API key is intended for admins only, so a member with a lower role can obtain it and call the public API on behalf of the organization. Both endpoints require a valid session, API key or OAuth token and are scoped to the caller's own organization. There is no anonymous access and no cross-tenant exposure. Impact if exploited ConfidentialityLow IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/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 Affects GitroomHQ GitroomHQ postiz-app NIST National Vulnerability DatabasePublished Oct 11, 2026 16:16 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee