PolicyPress information disclosure in CSS-only redaction
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.1
- Who is exposed
- Not reported
Summary
PolicyPress, a compliance policy management tool, has a flaw where sensitive content is exposed because web redaction relies only on CSS and because its starter workflow defaults are insecure. An attacker on the same local network who holds a low-privilege account and needs a user to take an action can read the sensitive content.
Written by a model
Original description
PolicyPress is a compliance policy management tool for small and mid-size teams. Prior to version 1.4.1, sensitive content is disclosed via CSS-only web redaction and insecure starter workflow defaults. This issue has been patched in version 1.4.1.
What to do
Upgrade to a fixed version: 1.4.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-68541 (PolicyPress: Sensitive content disclosed via CSS-only web redaction and insecure starter workflow defaults), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-68541 (entry last updated 2026-11-16):
Affected:
- sc2in PolicyPress: fixed in 1.4.1
Fixed versions: 1.4.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-68541 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68541 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sc2in/PolicyPress/security/advisories/GHSA-j557-r6p7-8r3m
- https://github.com/sc2in/PolicyPress/commit/131de241014c17c30130d83151da840d005d55d8
- https://github.com/sc2in/PolicyPress/releases/tag/v1.4.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-68541
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68541"}.Affected versions
- sc2in PolicyPressfixed in 1.4.1
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.2/10CVSS 5.2
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.18%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · sc2in/PolicyPress · Advisory GHSA-j557-r6p7-8r3m |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-68541 |
| Record | NVD · CVE-2026-68541 |
| Other links 2 | |
| Repository | GitHub · sc2in/PolicyPress · Commit 131de241 |
| Repository | GitHub · sc2in/PolicyPress · Release v1.4.1 |
Questions about CVE-2026-68541
Is CVE-2026-68541 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-68541?
PolicyPress: before 1.4.1.
Source: cve.now feed data
How do I fix CVE-2026-68541?
Upgrade to a fixed version: 1.4.1.
Source: cve.now feed data
Related
- CVE-2026-114516Etherpad: Pre-auth arbitrary file read
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- CVE-2026-131246Information Disclosure through REST API External Prompts in Splunk SOAR
- CVE-2026-59988django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS
- CVE-2026-61798netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
No corrections so far. Something wrong on this page? Report an error.