{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it identified a vulnerability in a SaaS product that does not require user action."
    }
  ],
  "id": "CVE-2025-34412",
  "lastModified": "2025-12-24T20:15:55.123",
  "metrics": {},
  "published": "2025-12-15T15:15:50.147",
  "references": [],
  "sourceIdentifier": "disclosure@vulncheck.com",
  "vulnStatus": "Rejected"
}

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "unknown",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Marco Ermini via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Hello everyone,\n\n\n\nKindly let me introduce myself. This is the first \u2013 and potentially, last \u2013 message on this mailing list. I am Marco, \nthe CISO of EQS Group. Kindly allow me to address some of the statements expressed publicly here.\n\n\n\nAbout the Convercent application\n\n\n\nConvercent was acquired by OneTrust in 2021, and in turn, EQS has acquired it from OneTrust at the end of 2024. Before \nbeing acquired by EQS, the Convercent application has not received much love in the latest years, and EQS has since \nthen proceeded to migrate its customers to the EQS Compliance COCKPIT, which is a modern, supported, and secure SaaS. \nThe Convercent application is sunset and will be finally switched off by mid of 2026.\n\n\n\nCurrently, Convercent is supported by EQS on a best-effort basis; despite that, EQS Group has committed to fix all \ncritical vulnerabilities until the last customer is fully migrated. We want our customers to migrate to our best \nservice because it is better \u2013 not rush them in our new product because what we inherited from an acquisition is \ninsecure.\n\n\n\n\n\nThe vulnerabilities\n\n\n\nThe two issues disclosed are either minor in nature or do not constitute vulnerabilities. One was a lack of certain \nHTTP headers (some of the reported ones where wrong, but regardless, still hardly something CVE-worthy), and the second \nwas about an \u201cexposed\u201d API; however, it is public by design as this is how the application works: it is a page where \ncustomers \u2013 who have explicitly agreed and signed off to be present \u2013 are added to a drop-down list, fed from this \npublic API. The web page exposes the list of customers by design.\n\n\n\nWhile we may reasonably question whether this page reflects current secure-by-design standards, this brings zero added \nrisk to any of the EQS customers and Convercent users.\n\n\n\nI strongly disagree with the ideas that those \u201cvulnerabilities\u201d could become CVEs \u2013 regardless of the status of the \nSaaS security and how CVEs are handled. Therefore, we proceeded to ask for their removal from the CVSS database, so not \nto alarm our customers with false positives. The responsible CNA agreed immediately to remove them (thank you very \nmuch, VulnCheck!).\n\n\n\n\n\nCommunication with our customers\n\n\n\nEQS Group communicates with its customers through established and appropriate channels \u2013 notably, our Trust Center \u2013 \nand not via anonymous mailing lists. Customers have received and will continue to receive all the notifications they \nhave contractually required to obtain, and where relevant, additional context beyond those obligations.\n\n\n\nCustomers have received a briefing about the activity happening on this mailing list via our Trust Center.\n\n\n\n\n\nThe status of SaaS Security\n\n\n\nAs EQS Group is a CNA candidate, we participate and closely follow discussions between MITRE, CISA, and the German BSI, \nabout vulnerability reporting for SaaS. While we have not heard any news on this front since the last two years, EQS \nGroup remains committed to aligning with applicable best practices as they evolve.\n\n\nWe believe that meaningful progress in SaaS security is best achieved through structured, collaborative forums with \nclear governance, rather than responding to ad-hoc reports of unvetted findings. EQS Group already participates to \nproper, professional working groups on SaaS security, for instance through the Cloud Security Alliance. If other \nworking groups will emerge through any of the official organisms already mentioned, we will certainly participate.\n\n\nIn general, as a principle, CVEs have been created many years ago, at a time where \u201cthe Cloud\u201d did not exist in its \ncurrent form. They were conceived so that users who procured a software from a development company and installed it on \ntheir system, could be notified when the software they have installed, manifested a security issue. In that way, they \ncould procure the patch and fix it before a misuse could happen.\n\n\nNow, except for very particular and edge cases, this is largely inapplicable to SaaS, where there is very little users \ncan do and solely rely on the Cloud Service Provider to fix any vulnerability. There is almost never any real ground \nfor a SaaS provider to notify a customer \u2013 unless of course a breach has been detected, but in that case we are way \nbeyond a CVE and we are on a different territory. For a SaaS, even knowing that the application had a bug, does not \nhelp the user in any way. This is why typically CVEs as a concept are not the proper tool to address SaaS \nvulnerabilities, and in general, rushing to disclose them only damages the users; a disclosure does not help them in \nany way.\n\n\n\n\nResponse to the \u201cResponsible\" Disclosure\n\n\n\nAbout the \u201cresponsible\" disclosure: EQS Group receives a significant volume of \u201cvulnerability notifications\u201d like that \none. Almost all of them are low or irrelevant issues from anonymous users looking to make a buck; they are typically \nabout a missing HTTP headers or lack of optional DNS records. Given the scale of our environment, it can happen that \nsome record is not updated, but this has little relevance to the security of our platforms. We also cannot always reply \nto all those messages, and most of them seem AI or automatically generated.\n\n\n\nThe notification from \u201cYuffie Kisaragi\u201d was sent to us on the 4th of December and went to Junk due to the low \nreputation of the email used. The author then rushed to obtain two CVE IDs less than two weeks later and subsequently \nlost no time posting them on this list.\n\n\n\nEQS Group is certainly not perfect, but if these would have been real vulnerabilities, I argue that this would have not \nqualified as a \u201cresponsible\u201d disclosure by any reasonable standard.\n\n\n\nFurther communications\n\n\nEQS Group\u2019s vulnerability handling policy is listed here\u003chttps://www.eqs.com/report-a-vulnerability/#handle\u003e \u2013  \nhttps://www.eqs.com/report-a-vulnerability/ \u2013 and we strongly suggest anyone to read it before they issue a report.\n\n\n\nIn this regard, we would like to point out the followings:\n\n  1.  For several reasons \u2013 legal, commercial, policy, and ethical \u2013 EQS Group is unable to respond to requests for \npayment of bounties outside of an official bug bounty program.\n  2.  EQS Group does nor remunerate bugs that were already discovered internally and were already in resolution.\n  3.  EQS Group strongly discourages non-approved, un-vetted testing on EQS Group\u2019s infrastructure. They can and will \nbe perceived as hostile activity. Testing is encouraged only within officially approved bug bounty programs, in respect \nto the established rules of engagement.\n  4.  Kindly avoid pointless reports on MTA-STS records, DMARC, quantum ciphers, and other junk like that. It makes our \nlife easier.\n\n\n\nThank you for your attention.\n\nBest regards / mit freundlichen Gr\u00fc\u00dfen / Cordiali saluti\n\nDr Marco Ermini (He/Him)\nChief Information Security Officer (CISO)\n\nMarco.Ermini () eqs com\u003cmailto:Marco.Ermini () eqs com;\u003e\n\n[LinkendIn]\u003chttps://www.linkedin.com/in/marcoermini/\u003e\nVereinbaren Sie einen Termin mit mir\u003chttps://outlook.office365.com/owa/calendar/BookaMeetingwithMarco () eqs \ncom/bookings/\u003e\n[EQS Group Logo]\u003chttps://www.eqs.com/?keyword=email-footer\u003e\n\n[EQS Compliance COCKPIT]\u003chttps://www.eqs.com/de/platform-compliance-ethics/?keyword=email-footer\u003e\nEQS Group GmbH | Karlstr. 47 | 80333 M\u00fcnchen | www.eqs.com\u003chttps://www.eqs.com/?keyword=email-footer\u003e | \nwww.integrityline.com\u003chttp://www.integrityline.com/?keyword=email-footer\u003e\n[linkedIn Logo]\u003chttps://www.linkedin.com/company/1273779\u003e\n[X Logo]\u003chttps://twitter.com/eqsgroup\u003e\n[Instagram Logo]\u003chttps://www.instagram.com/eqsgroup/\u003e\n[YouTube Logo]\u003chttps://www.youtube.com/user/EquityStory\u003e\n[RSS Logo]\u003chttps://www.eqs.com/compliance-knowledge/\u003e\n[Xing Logo]\u003chttps://www.xing.com/companies/eqsgroup\u003e\nRegister Court: Munich | Register Number: HRB 297048\nManaging Directors: Achim Weick (CEO), Andr\u00e9 Silverio Marques, Marcus Sultzer\n\nThe preceding email message contains information that is confidential and may constitute non-public information that is \nintended to be conveyed only to the designated recipient(s).\nIf you are not an intended recipient of this message, please notify the sender at +49 89 444430-000\u003ctel:+4989444430000\u003e.\nUnauthorized use, dissemination, distribution, or reproduction of this message is strictly prohibited and may be \nunlawful.\n\n\nFrom: Wade Sparks \u003cwsparks () vulncheck com\u003e\nDate: Wednesday, 21. January 2026 at 17:29\nTo: Yuffie Kisaragi \u003cyuffie.kisaragi () atomicmail io\u003e\nCc: Security Vulnerability \u003csecurity-vulnerability () eqs com\u003e, fulldisclosure () seclists org \u003cfulldisclosure () \nseclists org\u003e\nSubject: Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing \nPlatform (EQS Group)\n\n\nEXTERNAL EMAIL WARNING: Please check the sender of the message\n\nHello Yuffie,\n\nUpon further investigation, the VulnCheck CNA determined that these vulnerabilities were not suitable for CVE \nassignment. The vulnerabilities exist within a SaaS product and are mitigated at the CSP-level which in this case, \nwould be the vendor, EQS Group. Rather than contribute unactionable CVE records, the VulnCheck CNA used its \ndiscretionary prowess to move forward with rejecting these records. This policy aligns with a 2022 blog from \nMITRE\u003chttps://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID\u003e. It should be noted that the \nvendor informed us that they have published advisories for the respective vulnerabilities in their \"Trust Center\" \ncustomer portal.\n\nThese actions should not be a deterrent for you to pursue CVE assignment through MITRE or another research CNA.\n\nBest regards,\n\n[https://lh7-us.googleusercontent.com/-9dCGnQIZaW0ehyK1B0bqLmef7d7ZWuSmmmWUYJGhzNgtzRhqFPZrtO3AnQt8PETFHiv6_YST3DacZVgrxPdAYXErAMnJrF6Isn27caszruLjby7jLRuuU__5emkqFjU8hczQ307--yVVMpVSiK7Qg]\u003chttps://www.vulncheck.com/\u003e\n\nWade Sparks III\n\nVulnCheck\nSenior Vulnerability Analyst\n\n\nOn Tue, Jan 20, 2026 at 12:13\u202fPM Yuffie Kisaragi \u003cyuffie.kisaragi () atomicmail io\u003cmailto:yuffie.kisaragi () atomicmail \nio\u003e\u003e wrote:\n\n\nDear Art,\n\n\nThank you for sharing your detailed evaluation and for pointing out the relevant sections of the CNA Rules.\n\n\nYour argument is well reasoned, particularly with respect to the current guidance on SaaS and exclusively hosted \nservices.\n\n\nI have forwarded your evaluation to the CNA for further consideration. It will also be important to understand the \nvendor\u2019s perspective in light of the points you raised, especially regarding the applicability of the \n\u201cexclusively-hosted-service\u201d tag and the removal of prior restrictions.\n\nWe look forward to receive transparent feedback from the CNA and/or the vendor.\n\nTo date, the vendor has remained silent with regard to informing their users about the reported issues. As far as we \ncan determine, no public advisory or user-facing communication has been issued via their vulnerability reporting \nchannel (https://www.eqs.com/report-a-vulnerability/) or elsewhere.\n\nBest regards,\n\nYuffie\n\nOn Tue, Jan 20, 2026 at 7:26 PM \u003czmanion () protonmail com\u003cmailto:zmanion () protonmail com\u003e\u003e wrote:\n\nHi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking, despite being real, independently discovered, \nresponsibly disclosed, and acknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software. For a period of time, there was a restriction \nthat only the provider could make or request such an assignment. But the current CVE rules remove this restriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud, on-premises, artificial intelligence, machine \nlearning) as the sole basis for determining assignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411 and CVE-2025-34412 published and identify them \nas affecting an \"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag when all known Products listed in the CVE Record \nexist only as fully"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:41Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/25"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jan/25"
        },
        {
          "url": "http://www.integrityline.com/?keyword=email-footer"
        },
        {
          "url": "https://lh7-us.googleusercontent.com/-9dCGnQIZaW0ehyK1B0bqLmef7d7ZWuSmmmWUYJGhzNgtzRhqFPZrtO3AnQt8PETFHiv6_YST3DacZVgrxPdAYXErAMnJrF6Isn27caszruLjby7jLRuuU__5emkqFjU8hczQ307--yVVMpVSiK7Qg"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://outlook.office365.com/owa/calendar/BookaMeetingwithMarco"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://twitter.com/eqsgroup"
        },
        {
          "url": "https://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID"
        },
        {
          "url": "https://www.cve.org/resourcessupport/allresources/cnarules"
        },
        {
          "url": "https://www.eqs.com/?keyword=email-footer"
        },
        {
          "url": "https://www.eqs.com/compliance-knowledge/"
        },
        {
          "url": "https://www.eqs.com/de/platform-compliance-ethics/?keyword=email-footer"
        },
        {
          "url": "https://www.eqs.com/report-a-vulnerability/"
        },
        {
          "url": "https://www.eqs.com/report-a-vulnerability/#handle"
        },
        {
          "url": "https://www.instagram.com/eqsgroup/"
        },
        {
          "url": "https://www.linkedin.com/company/1273779"
        },
        {
          "url": "https://www.linkedin.com/in/marcoermini/"
        },
        {
          "url": "https://www.vulncheck.com/"
        },
        {
          "url": "https://www.xing.com/companies/eqsgroup"
        },
        {
          "url": "https://www.youtube.com/user/EquityStory"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jan/25"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-34411",
              "type": "related"
            },
            {
              "destId": "CVE-2025-34412",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0185",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/25",
            "automated": true,
            "contentSha256": "5706daeae34135987f816ff9f75eb733cc5a660d5099b81280a650892732ead3",
            "evidenceScore": 5,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/25",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-01-23T18:41:47Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0185"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:41Z",
    "dateUpdated": "2026-09-08T07:57:41Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0185"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "unknown",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Yuffie Kisaragi via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "UPDATE:\n\n\n\n\nFollowing the publication of these vulnerabilities and the subsequent CVE\nassignments, the CVE identifiers have now been revoked.\n\n\n\n\nThe vendor (EQS Group) contacted the CVE Program (via a CNA) and\u00a0disputed the\nrecords, stating that the affected product is an exclusively hosted SaaS\nplatform with no customer-managed deployment or versioning. Based on this\nargument, the CVE Program concluded that CVE assignment is \u201cnot a suitable\nsolution for vulnerability identification\u201d in this case, as customers do not\ntake direct action to apply fixes.\n\n\n\n\nIn other words, because the service is centrally hosted and patched at the\nprovider\u2019s discretion, the vulnerabilities are no longer considered eligible for\nCVE tracking, despite being real, independently discovered, responsibly\ndisclosed, and acknowledged by the vendor.\n\nThe vendor has stated that fixes are being implemented and that private customer\nnotifications will be issued internally.\n\n\n\n\nWhile remediation is of course welcome, this outcome highlights a broader issue:\nvulnerabilities in SaaS platforms can effectively disappear from public\nvulnerability tracking, simply because the deployment model removes user agency,\na model that arguably incentivizes security through obscurity, rather than\ntransparency.\n\n\n\n\nThe technical findings remain valid.\n\n\n\n\nThis update is shared purely for accuracy and record-keeping.\n\nOn Sun, Jan 4, 2026 at 4:40 PM \u003cyuffie.kisaragi () atomicmail io\n[yuffie.kisaragi () atomicmail io]\u003e wrote:\nUPDATE:\n\n\nThe reported vulnerabilities have now been assigned CVE identifiers:\nCVE-2025-34411: https://www.cve.org/cverecord?id=CVE-2025-34411\n[https://www.cve.org/cverecord?id=CVE-2025-34411]\nCVE-2025-34412: https://www.cve.org/cverecord?id=CVE-2025-34412\n[https://www.cve.org/cverecord?id=CVE-2025-34412]\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:41Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/4"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jan/4"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://www.cve.org/cverecord?id=CVE-2025-34411"
        },
        {
          "url": "https://www.cve.org/cverecord?id=CVE-2025-34412"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jan/4"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-34411",
              "type": "related"
            },
            {
              "destId": "CVE-2025-34412",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0195",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/4",
            "automated": true,
            "contentSha256": "f09c92da4c5a7aeb2581a72015cc49071ab139218b207121c182b6d3bc9d070c",
            "evidenceScore": 4,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/4",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-01-04T22:01:57Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0195"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:41Z",
    "dateUpdated": "2026-09-08T07:57:41Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0195"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "unknown",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Art Manion via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Hi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking, despite being real, independently discovered, \nresponsibly disclosed, and acknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software.  For a period of time, there was a restriction \nthat only the provider could make or request such an assignment.  But the current CVE rules remove this restriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud, on-premises, artificial intelligence, machine \nlearning) as the sole basis for determining assignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411 and CVE-2025-34412 published and identify them \nas affecting an \"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag when all known Products listed in the CVE Record \nexist only as fully hosted services. If the Vulnerability affects both hosted services and on-premises Products, then \nthis tag MUST NOT be used.\n\nRules: https://www.cve.org/resourcessupport/allresources/cnarules\n\nRegards,\n\n - Art\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:41Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/17"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jan/17"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://www.cve.org/resourcessupport/allresources/cnarules"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jan/17"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-34411",
              "type": "related"
            },
            {
              "destId": "CVE-2025-34412",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0197",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/17",
            "automated": true,
            "contentSha256": "d187d28957b37a8564bdb303fce20e7735192773826c8c243907db2920484f09",
            "evidenceScore": 5,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/17",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-01-08T18:26:44Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0197"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:41Z",
    "dateUpdated": "2026-09-08T07:57:41Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0197"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "unknown",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Yuffie Kisaragi via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Dear Art,\n\n\n\n\nThank you for sharing your detailed evaluation and for pointing out the relevant\nsections of the CNA Rules.\n\n\n\n\nYour argument is well reasoned, particularly with respect to the current\nguidance on SaaS and exclusively hosted services.\n\n\n\n\nI have forwarded your evaluation to the CNA for further consideration. It will\nalso be important to understand the vendor\u2019s perspective in light of the points\nyou raised, especially regarding the applicability of the\n\u201cexclusively-hosted-service\u201d tag and the removal of prior restrictions.\n\n\n\nWe look forward to receive transparent\u00a0feedback from the CNA and/or the vendor.\n\n\nTo date, the vendor has remained silent with regard to informing their users\nabout the reported issues. As far as we can determine, no public advisory or\nuser-facing communication has been issued via their vulnerability reporting\nchannel () or elsewhere.\n\n\nBest regards,\n\n\nYuffie\n\n\nOn Tue, Jan 20, 2026 at 7:26 PM \u003c\u003e wrote:\n\nHi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking,\ndespite being real, independently discovered, responsibly disclosed, and\nacknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software. For a\nperiod of time, there was a restriction that only the provider could make or\nrequest such an assignment. But the current CVE rules remove this restriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud, on-premises,\nartificial intelligence, machine learning) as the sole basis for determining\nassignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411 and\nCVE-2025-34412 published and identify them as affecting an\n\"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag when all\nknown Products listed in the CVE Record exist only as fully hosted services.\nIf the Vulnerability affects both hosted services and on-premises Products,\nthen this tag MUST NOT be used.\n\nRules: https://www.cve.org/resourcessupport/allresources/cnarules\n\nRegards,\n\n- Art\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:42Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/26"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jan/26"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://www.cve.org/resourcessupport/allresources/cnarules"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jan/26"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-34411",
              "type": "related"
            },
            {
              "destId": "CVE-2025-34412",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0213",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/26",
            "automated": true,
            "contentSha256": "16fb8f39abc59017249ab13d2d1e6c8331ea6508a7c71d74660b4fc553dabf06",
            "evidenceScore": 5,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/26",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-01-20T17:13:27Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0213"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:42Z",
    "dateUpdated": "2026-09-08T07:57:42Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0213"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "unknown",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Wade Sparks"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Hello Yuffie,\n\nUpon further investigation, the VulnCheck CNA determined that these\nvulnerabilities were not suitable for CVE assignment. The\nvulnerabilities exist within a SaaS product and are mitigated at the\nCSP-level which in this case, would be the vendor, EQS Group. Rather than\ncontribute unactionable CVE records, the VulnCheck CNA used its\ndiscretionary prowess to move forward with rejecting these records. This\npolicy aligns with a 2022 blog from MITRE\n\u003chttps://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID\u003e.\nIt\nshould be noted that the vendor informed us that they have published\nadvisories for the respective vulnerabilities in their \"Trust Center\"\ncustomer portal.\n\nThese actions should not be a deterrent for you to pursue CVE assignment\nthrough MITRE or another research CNA.\n\nBest regards,\n\n\u003chttps://www.vulncheck.com/\u003e\n\nWade Sparks III\nVulnCheck\nSenior Vulnerability Analyst\n\n\nOn Tue, Jan 20, 2026 at 12:13\u202fPM Yuffie Kisaragi \u003c\nyuffie.kisaragi () atomicmail io\u003e wrote:\n\n\n\nDear Art,\n\nThank you for sharing your detailed evaluation and for pointing out the\nrelevant sections of the CNA Rules.\n\nYour argument is well reasoned, particularly with respect to the current\nguidance on SaaS and exclusively hosted services.\n\nI have forwarded your evaluation to the CNA for further consideration. It\nwill also be important to understand the vendor\u2019s perspective in light of\nthe points you raised, especially regarding the applicability of the\n\u201cexclusively-hosted-service\u201d tag and the removal of prior restrictions.\n\nWe look forward to receive transparent feedback from the CNA and/or the\nvendor.\n\nTo date, the vendor has remained silent with regard to informing their\nusers about the reported issues. As far as we can determine, no public\nadvisory or user-facing communication has been issued via their\nvulnerability reporting channel (\nhttps://www.eqs.com/report-a-vulnerability/) or elsewhere.\n\nBest regards,\n\nYuffie\n\nOn Tue, Jan 20, 2026 at 7:26 PM \u003czmanion () protonmail com\u003e wrote:\n\nHi,\n\nthe vulnerabilities are no longer considered eligible for CVE tracking,\ndespite being real, independently discovered, responsibly disclosed, and\nacknowledged by the vendor.\nCVE IDs *can* be assigned for SaaS or similarly \"cloud only\" software.\nFor a period of time, there was a restriction that only the provider could\nmake or request such an assignment. But the current CVE rules remove this\nrestriction:\n\n4.2.3 CNAs MUST NOT consider the type of technology (e.g., cloud,\non-premises, artificial intelligence, machine learning) as the sole basis\nfor determining assignment.\n\nIt would have been acceptable (even preferred) to leave CVE-2025-34411\nand CVE-2025-34412 published and identify them as affecting an\n\"exclusively-hosted-service:\"\n\n5.1.11.1 (A CVE Record) MUST use the \u201cexclusively-hosted-service\u201d tag\nwhen all known Products listed in the CVE Record exist only as fully hosted\nservices. If the Vulnerability affects both hosted services and on-premises\nProducts, then this tag MUST NOT be used.\n\nRules: https://www.cve.org/resourcessupport/allresources/cnarules\n\nRegards,\n\n- Art\n\n\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T07:57:43Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/21"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jan/21"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://www.cve.org/Media/News/item/blog/2022/09/13/Dispelling-the-Myth-CVE-ID"
        },
        {
          "url": "https://www.cve.org/resourcessupport/allresources/cnarules"
        },
        {
          "url": "https://www.eqs.com/report-a-vulnerability/"
        },
        {
          "url": "https://www.vulncheck.com/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jan/21"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "Re: Multiple Security Misconfigurations and Customer Enumeration Exposure in Convercent Whistleblowing Platform (EQS Group)",
      "x_gcve": [
        {
          "recordType": "reference",
          "relationships": [
            {
              "destId": "CVE-2025-34411",
              "type": "related"
            },
            {
              "destId": "CVE-2025-34412",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0229",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jan/21",
            "automated": true,
            "contentSha256": "129a3df9c6db4589d4f36748522adb23150a18cc4a4a985706b7c7951e66992c",
            "evidenceScore": 5,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jan/21",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-01-21T16:29:03Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0229"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T07:57:43Z",
    "dateUpdated": "2026-09-08T07:57:43Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0229"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-34412"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-693"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-15T15:15:50Z",
    "severity": "MODERATE"
  },
  "details": "The Convercent Whistleblowing Platform operated by EQS Group contains a protection mechanism failure in its browser and session handling. By default, affected deployments omit HTTP security headers such as Content-Security-Policy, Referrer-Policy, Permissions-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, and Cross-Origin-Resource-Policy, and implement incomplete clickjacking protections. The application also issues session cookies with insecure or inconsistent attributes by default, including duplicate ASP.NET_SessionId values, an affinity cookie missing the Secure attribute, and mixed or absent SameSite settings. These deficiencies weaken browser-side isolation and session integrity, increasing exposure to client-side attacks, session fixation, and cross-site session leakage.",
  "id": "GHSA-2gvp-7c85-h6vg",
  "modified": "2025-12-15T15:30:32Z",
  "published": "2025-12-15T15:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-34412"
    },
    {
      "type": "WEB",
      "url": "https://seclists.org/fulldisclosure/2025/Dec/4"
    },
    {
      "type": "WEB",
      "url": "https://www.convercent.com"
    },
    {
      "type": "WEB",
      "url": "https://www.eqs.com/en-us/platform-convercent-clients"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/convercent-whisteblowing-platform-protection-mechanism-failure-insecure-default-browser-and-session-controls"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/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",
      "type": "CVSS_V4"
    }
  ]
}