`CVE-2026-87802`

Unknown No fix identified

Not yet in NVD's feed. The description, CVSS and CWE below come from the CVE Numbering Authority's own record, not from NVD analyst review. NVD's own page for this identifier may not exist yet.

Published yesterday. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.

Description

Improper verification of cryptographic signature vulnerability in Apache Syncope. When SRA is configured for OAuth 2.0 without JWKS set URI assigned, an attacker can forge arbitrary JWTs to impersonate any user identity and permissions, gaining full access to services proxied by SRA. This issue affects Apache Syncope: from 3.0.0-M0 through 3.0.16, from 4.0.0-M0 through 4.0.7, from 4.1.0-M0 through 4.1.2. Users are recommended to upgrade to version 4.0.8 / 4.1.3, which fix this issue.

CWE-347

Exploitation Status

No public exploit

Nothing published shows this CVE being exploited, which is not the same as ruling it out.

CVSS E:U

CISA KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS not scored

Waratek Defense Posture

No fix identified

In RASP's scope, but nothing published names a fix and nothing published shows an exploit. Neither of the two things VRT can act on exists, which is a claim about the available evidence, not about the vulnerability.

Protection none
Action not-needed
Review automated upstream-data
Record active

Decided by no-exploit : With no fix path, a public exploit, or a CISA record of one

Finding Resolved from QUEUED-FOR-REVIEW: this CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists.

Decided by	`no-exploit` : With no fix path, a public exploit, or a CISA record of one
Finding	Resolved from QUEUED-FOR-REVIEW: this CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists.

References

URL	Tags
https://lists.apache.org/thread/gx83cootj00kn8hqd73x1bp8441np33d	vendor-advisory

URL

Timeline

Published 2026-09-14 Last modified 2026-09-14

Published	2026-09-14	By the CVE Program.
NVD record modified	2026-09-14	NVD's own last-modified date for this record.

Published

2026-09-14

By the CVE Program.

NVD record modified

2026-09-14

NVD's own last-modified date for this record.

Pipeline policy audit (16 of 21 rules evaluated)

16 of 21 rules ran. The rest were never reached, because an earlier stage settled the CVE, a distinct claim from a rule that ran and found nothing.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? first match wins

1 rejected no-match CVE Program withdrawal of this identifier

scope: Is the vulnerability ARMR's to address? first match wins

2 armr-patch-file no-match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no-match An ARMR security-rule template on disk for this CVE

4 manual-classification no-match A researcher's recorded decision for this specific CVE

5 manual classification no-match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no-match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no-match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the native WebLogic proxy plug-in. Oracle gives these no CPE of their own and names them only in the description.

8 osv-maven no-match An OSV.dev record of this CVE affecting a package published to Maven Central

9 cna-maven-package matched Queued for review CNA declares the affected component is a Maven artifact

10 known-cpe-product not-reached An NVD CPE naming a product ARMR tracks

11 cna-cpe-product not-reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

12 oracle-advisory-family not-reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

13 non-deployable-product not-reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

14 unmatched-product not-reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? cumulative: every rule gets a turn

15 patch-hint no-match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

16 open-source-maven no-match The affected package being open source on Maven, so the fix can be read

17 poc-derivable no-match An indexed exploit to reverse-engineer, where there is no source to read

18 no-exploit decided it matched No fix identified No public exploits or POCs found in Exploit-DB, Nuclei templates, or GitHub POC repositories, and CISA's Vulnrichment assessment records no demonstrated exploit. No upstream fix reference or open-source Maven package was found either, so there is nothing to act on from either direction.

19 secure-rule-match no-match A vulnerability class already blocked by an ARMR security rule

20 below-action-threshold skipped Medium or Low severity, no KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

21 no-exploit-published skipped A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all

Raw stored JSON document for this CVE ↗ · NVD ↗ · CVE.org ↗