Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps AcyMailing Newsletter Team/Anti Spam and list cleaner – AcyChecker (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for AcyMailing Newsletter Team/Anti Spam and list cleaner – AcyChecker.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 13, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698)Also CWE-862
• Cross-repository issue/comment attachment re-linking can expose private attachment contentAlso CWE-862
• Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive Information to an Unauthorized Actor in code.gitea.io/giteaAlso CWE-862
• Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization settingAlso CWE-862
• Private Repository Metadata Remains Accessible After Access RevocationAlso CWE-862
• Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot accessAlso CWE-862

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps AcyMailing Newsletter Team/Anti Spam and list cleaner – AcyChecker (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for AcyMailing Newsletter Team/Anti Spam and list cleaner – AcyChecker.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 13, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• RSS/Atom feed handlers bypass API-token scope & public-only confinement (incomplete fix of #37698)Also CWE-862
• Cross-repository issue/comment attachment re-linking can expose private attachment contentAlso CWE-862
• Missing Authorization and Authorization Bypass Through User-Controlled Key and Incorrect Permission Assignment for Critical Resource and Exposure of Sensitive Information to an Unauthorized Actor in code.gitea.io/giteaAlso CWE-862
• Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization settingAlso CWE-862
• Private Repository Metadata Remains Accessible After Access RevocationAlso CWE-862
• Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot accessAlso CWE-862