Mardi 20 octobre 2026
148 CVE sur 788
-
CVE-2026-94266 – Non évaluée
curl
libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.
-
CVE-2026-94265 – Non évaluée
curl
When processing an HTTP redirect to a URL containing userinfo (a `username:password` component), curl might erroneously retain and re-transmit the original host's HTTP Negotiate authentication state. Consequently, a malicious server can trigger a redirect containing arbitrary userinfo to force curl to send a freshly minted Kerberos ticket—generated using the ambient identity of the client process to an untrusted third-party host, effectively bypassing the domain-scoping restrictions normally enforced by the absence of `--location-trusted`.
-
CVE-2026-92391 – Non évaluée
curl
A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within `curl_mime_free` leads to unbounded stack frame allocation during structure traversal, ultimately crashing the host process.
-
CVE-2026-92390 – Non évaluée
curl
When invoked with `--remote-header-name` (`-J`), curl fails to preserve its documented anti-clobbering protection if an intermediate 103 Early Hints response precedes the final HTTP response, or if an `ETag` header is processed before `Content-Disposition` under `--etag-save`. This flaw allows an HTTP(S) server to overwrite an existing local file specified in the `Content-Disposition` header despite the presence of the `-J` non-overwrite constraint.
-
CVE-2026-92389 – Non évaluée
curl
libcurl's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that forces the client into transmit mode, prompting libcurl to consume and transmit data from the handle's persistent `CURLOPT_READDATA` pointer - including data remaining from unrelated prior operations, such as an HTTP POST request executed on a reused handle.
-
CVE-2026-92388 – Non évaluée
curl
When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of this handle triggers an immediate crash, and cloning it via `curl_easy_duphandle()` copies this corrupted state into the duplicate. If the original handle is subsequently freed, executing a transfer on the cloned handle causes a heap use-after-free read against the dangling handle reference; alternatively, reusing the original or cloned handle while changing only `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`) results in type confusion, forcing the internal parser to interpret incoming server response bytes into memory at the application-supplied write data pointer.
-
CVE-2026-92387 – Non évaluée
curl
By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can exploit libcurl and completely bypass its configured transfer timeout mechanism, indefinitely blocking all concurrent transfers bound to the same multi-handle.
-
CVE-2026-92386 – Non évaluée
curl
When writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make `curl` write a record that exceeds its line-length parsing limit. Consequently, any subsequent `curl` invocation reading from that same cookie jar using `--cookie` silently aborts parsing prematurely upon encountering the too long line, ignoring all subsequent valid cookies in the file.
-
CVE-2026-87866 – Non évaluée
curl
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field - extracts and matches a different embedded key, incorrectly authorizing the pinned public key.
-
CVE-2026-87865 – Non évaluée
curl
When libcurl uses libssh2 with a hashed `known_hosts` file, an unrelated initial entry can cause host key validation to report a key *mismatch* as a *missing* key to the `CURLOPT_SSH_KEYFUNCTION` callback.
-
CVE-2026-87864 – Non évaluée
curl
Enabling `CURLOPT_CRLF` causes curl to advertise the raw input byte count in the `IMAP APPEND {N}` literal while transmitting line-ending expanded data. The server reads only $N$ bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session.
-
CVE-2026-87863 – Non évaluée
curl
An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.
-
CVE-2026-87862 – Non évaluée
curl
Importing a `includeSubDomains` parent HSTS entry before a longer-lived child entry, silently drops the child. Consequently, when the parent expires, the child's valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than upgrading to HTTPS.
-
CVE-2026-87861 – Non évaluée
curl
When using ambient user credentials, an HTTP request directed to one origin may be dispatched over a connection previously authenticated via Negotiate for a different origin, leaving the request's intended credentials unused.
-
CVE-2026-86415 – Non évaluée
curl
libcurl's connection cache match function never considers the automatic client certificate option, so a cached, already authenticated Schannel connection can be handed to a transfer that got redirected to a different origin, even though the code explicitly switched off the auto client cert option for that transfer to prevent exactly this.
-
CVE-2026-86414 – Non évaluée
curl
An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the `CONNECT` tunnel request with 401 `WWW-Authenticate:` instead of the expected 407 `Proxy-Authenticate:`.
-
CVE-2026-107929 – Non évaluée
curl
When `CURLOPT_INTERFACE` (or the command line tool's `--interface` option) is set with one of the documented prefixes (`if!`, `host!`, `ifhost!`), that binding is not part of the connection reuse key, so a later transfer asking for a different source can silently reuse an existing connection and go out from the earlier transfer's source address
-
CVE-2026-107928 – Non évaluée
curl
When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when `gnutls_record_send()` returns a number of bytes sent **greater than the number of bytes it was given to send**. GnuTLS does that after a blocked send.
-
CVE-2026-86413 – Non évaluée
curl
When using an *ambient user* in a first transfer doing Negotiate authentication and asked to follow redirects, curl could pass on its credential details to an unrelated second origin when asked to redirect there.
-
CVE-2026-86412 – Non évaluée
curl
A remote HTTP server can set a cookie that curl accepts and writes to a Netscape cookie jar but cannot reload. On the next invocation using the same path for `--cookie` and `--cookie-jar`, curl fails before connecting, then the cleanup procedure replaces the jar with an empty file, deleting cookies for unrelated domains.
-
CVE-2026-86411 – Non évaluée
curl
An `ftp://` transfer configured with `CURLUSESSL_NONE` can reuse a pooled FTP control connection that a previous easy handle upgraded with `STARTTLS` and authenticated using a client certificate. The second handle performs neither a new TLS handshake nor a new FTP login, so the server continues to authorize it under the first handle's certificate identity.
-
CVE-2026-86410 – Non évaluée
curl
A flaw in the curl command line tool's logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect.
-
CVE-2026-86409 – Non évaluée
curl
Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking state information.
-
CVE-2026-113867 – Non évaluée
Mozilla Thunderbird
Thunderbird did not escape attribute values when serializing outgoing XMPP stanzas. Because values from incoming requests were echoed back in automatic replies, a remote XMPP user could send a crafted request that caused Thunderbird to inject arbitrary stanzas into the user's connection, which the server would then process as if sent by the user. This could be used to send messages or change contact and subscription settings on behalf of the user, without any interaction. This bug only affects Thunderbird's chat feature with XMPP accounts. This vulnerability was fixed in Thunderbird 158.0.1 and Thunderbird 153.5.1.
-
CVE-2026-113399 – Non évaluée
Mozilla Firefox · Mozilla Thunderbird
Incorrect boundary conditions in the SVG component. This vulnerability was fixed in Firefox 158.0.1 and Thunderbird 158.0.1.
-
CVE-2026-34485 – Non évaluée
Nokia 1830 Global Express (GX)
Nokia 1830 Global Express (GX) is vulnerable to a CLI ACL Bypass vulnerability where a low-privileged authenticated attacker can bypass the SSH isolation mechanism and gain access to the underlying operating system shell via a custom SSH command. This issue occurs by default in the system and is not the result of misconfiguration.
-
CVE-2026-34484 – Non évaluée
Nokia 1830 Global Express (GX)
Nokia 1830 Global Express GX is vulnerable to a local privilege escalation vulnerability which exists in the administrative shell interface. An authenticated local attacker with restricted shell access can exploit this vulnerability to bypass local security restrictions and gain root access on the device.
-
CVE-2026-93446 – Non évaluée
Apache Software Foundation Apache Tomcat
Incomplete cleanup vulnerability in Apache Tomcat could cause TLS 1.3 connections to fail intermittently. This issue affects Apache Tomcat: from 11.0.0-M21 through 11.0.26, from 10.1.25 through 10.1.60, from 9.0.90 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
-
CVE-2026-80353 – Non évaluée
Apache Software Foundation Apache Tomcat
Time-of-check time-of-use (TOCTOU) race condition vulnerability in Apache Tomcat when creating unix domain sockets for the APR/Native connector allows an unauthorised local user to access the unix domain socket. The fix for CVE-2026-65183 only addressed the NIO connector. It did not address the same issue in the APR/Native connector. This issue affects Apache Tomcat: from 9.0.47 through 9.0.122. Users are recommended to upgrade to version 9.0.123, which fixes the issue.
-
CVE-2026-74049 – Non évaluée
Apache Software Foundation Apache Tomcat
Execution After Redirect (EAR) vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.26, from 10.1.0-M1 through 10.1.60, from 9.0.0.M1 through 9.0.122. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.27, 10.1.61, 9.0.123, which fixes the issue.
-
CVE-2026-74048 – Non évaluée
Apache Software Foundation Apache Tomcat
Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activation fails, Tomcat logs and error but continues to use JSSE in non-FIPS mode with the provided configuration. This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.26, from 10.1.22 through 10.1.60, from 9.0.92 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
-
CVE-2026-92287 – Non évaluée
Apache Software Foundation Apache Arrow C++ · Apache Software Foundation PyArrow
Pass-through of unvalidated KMS URLs to KMS clients in Apache C++ Parquet and PyArrow versions 4.0.0 to 25.0.1. This affects users who read Parquet files and configure Parquet decryption properties with a KmsClient implementation. On the reader side, the KMS URL can be application-controlled (specified in the KmsConnectionConfig) or file-controlled. If the user does not leverage application control for this parameter, a file-controlled KMS URL is forwarded to a pluggable KmsClient implementation. If the KMS implementation does not perform host validation and makes use of the provided KMS URL, a KMS token can be sent to a malicious host set by an attacker in the file. Users are recommended to upgrade to version 26.0.0, which disables this behavior by default and requires that users opt-in to it by enabling the read_kms_url flag in the DecryptionConfiguration. Users of affected versions are recommended to either specify the KMS URL in the KmsConnectionConfig when reading files, or ensure any KmsClient implementations validate received KMS URLs. Users that opt-in to file-controlled KMS URLs in version 26.0.0 and later must ensure KmsClients validate KMS URLs.
-
CVE-2026-86467 – Non évaluée
Apache Software Foundation Apache Airflow Amazon provider
Apache Airflow Amazon provider: the AWS auth manager's SAML login flow does not bind the authentication response to the browser that began it. The login handler discards the AuthnRequest ID and the callback validates the assertion without requiring a matching InResponseTo, so an unauthenticated attacker who can cause a victim to load a page can complete a SAML login in the victim's browser using the attacker's own assertion, silently logging the victim into the attacker's Airflow account. Subsequent work the victim performs lands in a session the attacker controls. Affects deployments using the AWS auth manager with SAML authentication. The victim needs only to visit an attacker-controlled page; no Airflow account or credential is required of the attacker. This is the same login-CSRF class fixed in the Keycloak auth manager as CVE-2026-40948. Users of apache-airflow-providers-amazon are recommended to upgrade to version 9.38.0, which fixes the issue.
-
CVE-2026-88041 – Non évaluée
Apache Software Foundation Apache Tomcat
Incomplete cleanup vulnerability in Apache Tomcat allowed an trailer information from a previous request to leak into a subsequent request. This issue affects Apache Tomcat: from 11.0.0-M23 through 11.0.26, from 10.1.27 through 10.1.60, from 9.0.92 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
-
CVE-2026-108088 – Non évaluée
Apache Software Foundation Apache Cocoon
** UNSUPPORTED WHEN ASSIGNED ** Use of cache containing sensitive information vulnerability in Apache Cocoon. When using the cache on a multi-user application, cached values for one user could be used when serving content for other users. This issue affects Apache Cocoon: all versions. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
-
CVE-2026-108087 – Non évaluée
Apache Software Foundation Apache Cocoon
** UNSUPPORTED WHEN ASSIGNED ** Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Apache Cocoon. This issue affects Apache Cocoon: all versions. Missing input sanitation would allow arbitrary SQL injection through the SQL processor or sql:/esql: logicsheets. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
-
CVE-2026-108086 – Non évaluée
Apache Software Foundation Apache Cocoon
** UNSUPPORTED WHEN ASSIGNED ** Improper restriction of recursive entity references in DTDs ('XML entity expansion') vulnerability in Apache Cocoon. This issue affects Apache Cocoon: all versions. XEE in the fp: form processor could lead to SSRF, including exposing files from the server to an untrusted external system As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
-
CVE-2026-97406 – Non évaluée
Xerj Console API
XERJ Console API bearer tokens can bypass the passkey‑only authentication requirement and directly invoke the API‑token creation endpoint, allowing unauthorized minting of persistent successor credentials.
-
CVE-2026-111946 – Non évaluée
Plack::Middleware::ETag versions from 0.04 before 0.06 for Perl disclose file inode numbers in the default ETag header. When the response body is a filehandle and the file_etag option is not set, the ETag is built from the file's inode number, modification time and size. Clients receiving affected responses may use the disclosed inode numbers to aid backend fingerprinting and correlation of files served through different URLs.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
Rejected reason: this CVE was issued in error.
-
CVE-2026-86977 – Non évaluée
Apple iOS and iPadOS
An authorization issue was addressed with improved network restrictions. This issue is fixed in iOS 27 and iPadOS 27. An app may be able to initiate calls or send messages.
-
CVE-2026-86959 – Non évaluée
Apple iOS and iPadOS · Apple macOS
An input validation issue was addressed with improved input validation. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. Processing a maliciously crafted image may lead to unexpected process termination.
-
CVE-2026-86944 – Non évaluée
Apple iOS and iPadOS · Apple macOS
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 26.7 and iPadOS 26.7, macOS Sequoia 15.8, macOS Tahoe 26.7. An app may be able to cause unexpected system termination.
-
CVE-2026-86935 – Non évaluée
Apple macOS
This issue was addressed by removing additional entitlements. This issue is fixed in macOS Golden Gate 27. An app may be able to access user-sensitive data.
-
CVE-2026-86868 – Non évaluée
Apple macOS
An authentication issue was addressed with improved state management. This issue is fixed in macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7. An attacker may be able to impersonate other users.
-
CVE-2026-84582 – Non évaluée
Apple iOS and iPadOS · Apple macOS · Apple tvOS · Apple visionOS
A privacy issue was addressed with improved access restrictions. This issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27, watchOS 27. An app may be able to access sensitive user data.
-
CVE-2026-28854 – Non évaluée
Apple macOS
The issue was addressed with additional app bundle integrity checks. This issue is fixed in macOS Golden Gate 27. A maliciously modified app may not be prevented from launching.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.
-
Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.