DevSecOps and application security
JFrog Security advisories: every record the registers tie to its products
In one line
15 advisories are attributed to JFrog Security products in this record, covering July 2022 to January 2026, and none of them appears in the CISA catalogue of known exploited vulnerabilities. A further 0 register entries mention JFrog Security without naming one of its products as affected, and are excluded rather than counted. Each entry below links to the register that published it.
Attributed
15
tied to a named product
Known exploited
0
in the CISA catalogue
Rated critical
0
by the register
Last checked
Jul 18, 2026
sources re-queried
Why this list is shorter than a CVE mirror
The registers are searched by keyword, so a search for a company name returns advisories that merely mention it. A mirror publishes those. This page does not: an entry appears only when the register itself ties it to a product of JFrog Security, through a reference on the vendor's own domain, the vendor named as the assigning authority, or the affected product list naming it.
0 entries did not clear that bar and are not shown. That is the difference, and it is deliberate: a page that lists another company's vulnerability under this heading is wrong in the way that matters most.
15 of the 15 records carry a CVSS base score from the register. Where none is published, none is shown, and no score is estimated.
The full list, most recently exploited and most recent first
Records held by several registers are folded into one entry with a link to each, so the same vulnerability is not counted twice. Entries listed in the CISA catalogue of known exploited vulnerabilities are shown first, because that is the one flag on this page that changes what a reader should do next.
- WID-SEC-2026-0004mediumCVSS 4.9Jan 05, 2026
Affected products: JFrog Artifactory
- WID-SEC-2022-2133lowCVSS 1.6Nov 19, 2025
Affected products: HCL Domino, JFrog Artifactory, Atlassian Bitbucket
- WID-SEC-2022-1375highCVSS 10.0Oct 13, 2025
Affected products: Red Hat Enterprise Linux, Ubuntu Linux, SUSE Linux, JFrog Artifactory
- WID-SEC-2024-0628highCVSS 8.8Nov 25, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-0416highCVSS 8.8Nov 12, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-1765highCVSS 9.3Aug 06, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-1157mediumCVSS 6.4May 16, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-1021mediumCVSS 7.8May 03, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-0884mediumCVSS 6.5Apr 17, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-0584mediumCVSS 7.2Mar 08, 2024
Affected products: JFrog Artifactory
- WID-SEC-2024-0573highCVSS 9.3Mar 07, 2024
Affected products: JFrog Artifactory
- WID-SEC-2023-3178mediumCVSS 5.5Dec 20, 2023
Affected products: JFrog Artifactory
- WID-SEC-2023-2536mediumCVSS 6.5Oct 04, 2023
Affected products: JFrog Artifactory
- WID-SEC-2023-0037mediumCVSS 5.3Jan 09, 2023
Affected products: JFrog Artifactory
- WID-SEC-2022-0562mediumCVSS 6.1Jul 05, 2022
Affected products: JFrog Artifactory
Which registers contributed
| Register | Operated by | Entries | Latest |
|---|---|---|---|
| CERT-Bund security advisories | BSI, Federal Republic of Germany | 15 | Jan 05, 2026 |
The entry counts here are the raw register totals for JFrog Security, before attribution. They are larger than the list above for exactly that reason.
Questions this page answers
How many vulnerabilities does JFrog Security have?
15 advisories in this record are tied by a register to a product of JFrog Security. That is not the same as the number of vulnerabilities the products contain, and no public source knows that number. It is the count of what has been found, disclosed and published, which depends on how much the products are examined and how openly the vendor discloses.
Are any JFrog Security vulnerabilities being actively exploited?
None of the 15 records here appears in the CISA catalogue of known exploited vulnerabilities. That catalogue is not exhaustive: it lists what CISA has confirmed as exploited, so absence from it is not proof that nothing has been exploited.
Why does this page show fewer CVEs for JFrog Security than other sites?
Because a keyword search for a company name returns advisories about other companies' products that mention it in passing, and this page excludes those. 0 register entries name JFrog Security without naming one of its products as affected. A mirror that lists them produces a longer page and a wrong number.
Where do the JFrog Security advisories on this page come from?
From CERT-Bund security advisories (BSI, Federal Republic of Germany). Every entry links back to the register that published it, and carries the date that register states. Where the same vulnerability is held by several registers it is shown once with a link to each, rather than counted twice.
Does a long advisory list mean JFrog Security is insecure?
No. A register records what researchers found and what the vendor disclosed, so a widely deployed product with a working disclosure process accumulates more entries than one nobody examines. A short list can equally mean a small install base or a vendor that publishes little. This page reports the record and does not rate the vendor, because whether this is acceptable depends on your risk appetite, your compliance scope and the alternatives you are weighing.
A list of advisories is not a risk assessment
What matters is which of these touch the components you actually run, in the configuration you actually run them in, and whether that is acceptable next to the alternatives on your shortlist. DecisionOS reads the same pool against the criteria of a real decision and produces a memo that holds up in front of a board and an auditor.
The full JFrog Security record, including sources and open questions