CVE-2026-119763: changelog.com: missing authz exposes unpublished content

MEDIUM

Published October 30, 2026

CISO Take

changelog.com, the open-source publishing platform behind the Changelog podcast and newsletter, has a missing-authorization flaw (CWE-862) in its preview routes. Anyone on the internet can read draft posts, unsent newsletters and declined news items by guessing identifiers, with no login. The CVSS score is a moderate 5.3 and only confidentiality is affected, with no integrity or availability impact. There is no KEV listing, no public exploit, no Nuclei template and no EPSS data, so exploitation pressure is low. The AI link is tenuous: this is a content-publishing web app, not an AI/ML framework, and we found no tracked AI package affected. If your organization runs a fork or self-hosted instance, pull the fix from commit 7b35e829 and treat any pre-release material kept in drafts as potentially exposed. Otherwise, track this as low priority.

Sources:NVDATLASvulncheck.comgithub.com/thechangelog/changelog.comhackmd.io

What is the risk?

Low to medium overall. Exploitation is trivial: the network is the attack vector, complexity is low, and no privileges or user interaction are needed. Impact is limited to confidentiality of unpublished editorial content (CVSS C:L). There is no sign of active exploitation: it is not in CISA KEV, there is no public exploit or scanner template, and EPSS is unavailable. The affected range and patched version are not formally specified, only the fix commit. Exposure applies only to organizations running changelog.com code (self-hosted or forked). AI/ML systems are not directly at risk.

How does the attack unfold?

Reconnaissance

Attacker identifies a changelog.com instance and its preview route patterns for posts, newsletters and news items.

AML.T0006

Enumeration

Attacker iterates hashid post IDs, sequential newsletter slugs and integer news IDs against unauthenticated preview endpoints.

AML.T0049

Data Access

Preview controllers return content without authorization checks, exposing draft posts, unsent newsletters and declined news items.

AML.T0036

Impact

Unpublished editorial content is disclosed, enabling premature leaks, embargo breaches or competitive intelligence gathering.

Reconnaissance

Attacker identifies a changelog.com instance and its preview route patterns for posts, newsletters and news items.

AML.T0006

Enumeration

Attacker iterates hashid post IDs, sequential newsletter slugs and integer news IDs against unauthenticated preview endpoints.

AML.T0049

Data Access

Preview controllers return content without authorization checks, exposing draft posts, unsent newsletters and declined news items.

AML.T0036

Impact

Unpublished editorial content is disclosed, enabling premature leaks, embargo breaches or competitive intelligence gathering.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
changelog.com	—	—	No patch

Do you use changelog.com? You're affected.

How severe is it?

CVSS 3.1

5.3 / 10

EPSS

0.5%

chance of exploitation in 30 days

Higher than 42% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AVNetwork

ACLow

PRNone

UINone

SUnchanged

CLow

INone

ANone

What should I do?

5 steps

Update to a build that includes upstream commit 7b35e82934be93e8b0064299a611c98d55b3e0eb, or cherry-pick the fix if you run a fork.
Until patched, restrict the preview routes (post, news issue and news item previews) at the reverse proxy or WAF to authenticated or internal users.
Review web access logs for unauthenticated, high-volume or sequential requests to preview endpoints, especially enumeration of slugs and integer IDs.
Assume any draft content may have been read and avoid keeping sensitive or embargoed material in unpublished states on affected instances.
Track the upstream issue (thechangelog/changelog.com#581) and the VulnCheck advisory for the formal affected-version range.

How is it classified?

Auth BypassData LeakageAPIAML.T0049- Exploit Public-Facing Application

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-119763?

Is CVE-2026-119763 actively exploited?

No confirmed active exploitation of CVE-2026-119763 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-119763?

1. Update to a build that includes upstream commit 7b35e82934be93e8b0064299a611c98d55b3e0eb, or cherry-pick the fix if you run a fork. 2. Until patched, restrict the preview routes (post, news issue and news item previews) at the reverse proxy or WAF to authenticated or internal users. 3. Review web access logs for unauthenticated, high-volume or sequential requests to preview endpoints, especially enumeration of slugs and integer IDs. 4. Assume any draft content may have been read and avoid keeping sensitive or embargoed material in unpublished states on affected instances. 5. Track the upstream issue (thechangelog/changelog.com#581) and the VulnCheck advisory for the formal affected-version range.

What systems are affected by CVE-2026-119763?

This vulnerability affects the following AI/ML architecture patterns: Content publishing platforms, Web applications with preview/draft workflows.

What is the CVSS score for CVE-2026-119763?

CVE-2026-119763 has a CVSS v3.1 base score of 5.3 (MEDIUM). The EPSS exploitation probability is 0.49%.

What is the AI security impact?

Affected AI Architectures

Content publishing platformsWeb applications with preview/draft workflows

MITRE ATLAS Techniques

AML.T0049Exploit Public-Facing Application

What are the technical details?

Original Advisory

changelog.com before commit 7b35e829 contains a missing authorization vulnerability that allows unauthenticated attackers to read unpublished content via preview routes in PostController, NewsIssueController and NewsItemController. Attackers can enumerate hashid post IDs, sequential newsletter slugs and integer news IDs against preview endpoints to read draft posts, unsent newsletters and declined news items.

Exploitation Scenario

An attacker scripts requests against the preview endpoints without authenticating. They iterate integer news IDs, sequential newsletter slugs and candidate hashid post IDs, and collect any response that returns content. This surfaces draft articles, newsletters not yet sent and news items that editors declined to publish. In an AI-related context, this could leak unreleased commentary on AI security topics or editorial plans before publication, giving a competitor or threat actor early insight or the ability to leak embargoed material. The attack needs no special skills and no AI knowledge.

Weaknesses (CWE)

CWE-862Missing Authorization

CWE-862 — Missing Authorization: The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

[Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
[Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.